Minikube: Configuration - Revision history

Onnowpurbo: /* Making environment values persistent */

2023-05-08T07:37:43Z

Making environment values persistent

Onnowpurbo: /* Exclusive environment tuning */

2023-05-08T07:35:25Z

Exclusive environment tuning

Onnowpurbo: /* Environment variable */

2023-05-08T07:24:05Z

Environment variable

Onnowpurbo: /* Modifying Kubernetes defaults */

2023-05-08T02:45:11Z

Modifying Kubernetes defaults

Onnowpurbo: /* Memilih versi Kubernetes */

2023-05-08T02:40:45Z

Memilih versi Kubernetes

Onnowpurbo: /* Selecting a Kubernetes version */

2023-05-08T02:33:45Z

Selecting a Kubernetes version

Onnowpurbo: /* Persistent Configuration */

2023-05-08T02:08:57Z

Persistent Configuration

Onnowpurbo at 01:57, 8 May 2023

2023-05-08T01:57:53Z

Onnowpurbo: Created page with "Sumber: https://minikube.sigs.k8s.io/docs/handbook/config/ Configuration Configuring your cluster Basic Configuration Most minikube configuration is done via the flags inter..."

2023-05-06T01:20:58Z

Created page with "Sumber: https://minikube.sigs.k8s.io/docs/handbook/config/ Configuration Configuring your cluster Basic Configuration Most minikube configuration is done via the flags inter..."

New page

Sumber: https://minikube.sigs.k8s.io/docs/handbook/config/

Configuration
Configuring your cluster
Basic Configuration
Most minikube configuration is done via the flags interface. To see which flags are possible for the start command, run:

minikube start --help
Persistent Configuration
minikube allows users to persistently store new default values to be used across all profiles, using the minikube config command. This is done providing a property name, and a property value.

For example, to persistently configure minikube to use hyperkit:

minikube config set driver hyperkit
You can get a complete list of configurable fields using:

minikube config --help
To get a list of the currently set config properties:

minikube config view
Kubernetes configuration
minikube allows users to configure the Kubernetes components with arbitrary values. To use this feature, you can use the --extra-config flag on the minikube start command.

This flag is repeated, so you can pass it several times with several different values to set multiple options.

Selecting a Kubernetes version
By default, minikube installs the latest stable version of Kubernetes that was available at the time of the minikube release. You may select a different Kubernetes release by using the --kubernetes-version flag, for example:

minikube start --kubernetes-version=v1.11.10
minikube follows the Kubernetes Version and Version Skew Support Policy, so we guarantee support for the latest build for the last 3 minor Kubernetes releases. When practical, minikube aims to support older releases as well so that users can emulate legacy environments.

For up to date information on supported versions, see OldestKubernetesVersion and NewestKubernetesVersion in constants.go

Enabling feature gates
Kubernetes alpha/experimental features can be enabled or disabled by the --feature-gates flag on the minikube start command. It takes a string of the form key=value where key is the component name and value is the status of it.

minikube start --feature-gates=EphemeralContainers=true
Modifying Kubernetes defaults
The kubeadm bootstrapper can be configured by the --extra-config flag on the minikube start command. It takes a string of the form component.key=value where component is one of the strings

kubeadm
kubelet
apiserver
controller-manager
scheduler
and key=value is a flag=value pair for the component being configured. For example,

minikube start --extra-config=apiserver.v=10 --extra-config=kubelet.max-pods=100
For instance, to allow Kubernetes to launch on an unsupported Docker release:

minikube start --extra-config=kubeadm.ignore-preflight-errors=SystemVerification
Runtime configuration
The default container runtime in minikube varies. You can select one explicitly by using:

minikube start --container-runtime=docker
Options available are:

containerd
cri-o
docker
See https://kubernetes.io/docs/setup/production-environment/container-runtimes/

Environment variables
minikube supports passing environment variables instead of flags for every value listed in minikube config. This is done by passing an environment variable with the prefix MINIKUBE_.

For example the minikube start --iso-url="$ISO_URL" flag can also be set by setting the MINIKUBE_ISO_URL="$ISO_URL" environment variable.

Exclusive environment tunings
Some features can only be accessed by minikube specific environment variables, here is a list of these features:

MINIKUBE_HOME - (string) sets the path for the .minikube directory that minikube uses for state/configuration. If you specify it to /path/to/somewhere and somewhere is not equal to .minikube, the final MINIKUBE_HOME will be /path/to/somewhere/.minikube. Defaults to ~/.minikube if unspecified. Please note: this is used only by minikube and does not affect anything related to Kubernetes tools such as kubectl.

MINIKUBE_IN_STYLE - (bool) manually sets whether or not emoji and colors should appear in minikube. Set to false or 0 to disable this feature, true or 1 to force it to be turned on.

CHANGE_MINIKUBE_NONE_USER - (bool) automatically change ownership of ~/.minikube to the value of $SUDO_USER

MINIKUBE_ENABLE_PROFILING - (int, 1 enables it) enables trace profiling to be generated for minikube

MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE - (bool) suppresses Docker performance warnings when Docker is slow

Example: Disabling emoji
Linux
macOS
Windows
export MINIKUBE_IN_STYLE=false
minikube start
Making environment values persistent
To make the exported variables persistent across reboots:

Linux and macOS: Add these declarations to ~/.bashrc or wherever your shells environment variables are stored.
Windows: Either add these declarations to your ~\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 or run the following in a PowerShell terminal:
[Environment]::SetEnvironmentVariable("key", "value", [EnvironmentVariableTarget]::User)

==Referensi==

* https://minikube.sigs.k8s.io/docs/handbook/config/

==Pranala Menarik==

* [[minikube]]

@@ Line 104: / Line 104: @@
   minikube start
-==Making environment values persistent==
+==Membuat nilai environment persisten==
-To make the exported variables persistent across reboots:
+Untuk membuat variabel yang diekspor presistent ada saat reboot:
-* Linux and macOS: Add these declarations to ~/.bashrc or wherever your shells environment variables are stored.
+* Linux dan macOS: Tambahkan deklarasi ini ke ~/.bashrc atau di mana pun variabel environment shell disimpan.
-* Windows: Either add these declarations to your ~\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 or run the following in a PowerShell terminal:
+* Windows: Tambahkan deklarasi ini ke ~\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 atau jalankan perintah berikut di terminal PowerShell:
   [Environment]::SetEnvironmentVariable("key", "value", [EnvironmentVariableTarget]::User)

@@ Line 79: / Line 79: @@
 Lihat https://kubernetes.io/docs/setup/production-environment/container-runtimes/
-==Environment variable==
+==Environment variabel==
-minikube supports passing environment variables instead of flags for every value listed in minikube config. This is done by passing an environment variable with the prefix MINIKUBE_.
+minikube mendukung penerusan environment variabel bukan flag untuk setiap nilai yang tercantum dalam konfigurasi minikube. Ini dilakukan dengan meneruskan environmenyal variabel dengan prefix MINIKUBE_.
-For example the minikube start --iso-url="$ISO_URL" flag can also be set by setting the MINIKUBE_ISO_URL="$ISO_URL" environment variable.
+Contoh
 ==Exclusive environment tuning==

@@ Line 91: / Line 91: @@
 ==Exclusive environment tuning==
-Some features can only be accessed by minikube specific environment variables, here is a list of these features:
+Beberapa fitur hanya dapat diakses oleh environment variabel spesifik minikube, berikut adalah daftar fitur tersebut:
-MINIKUBE_HOME - (string) sets the path for the .minikube directory that minikube uses for state/configuration. If you specify it to /path/to/somewhere and somewhere is not equal to .minikube, the final MINIKUBE_HOME will be /path/to/somewhere/.minikube. Defaults to ~/.minikube if unspecified. Please note: this is used only by minikube and does not affect anything related to Kubernetes tools such as kubectl.
+* MINIKUBE_HOME - (string) menetapkan path untuk direktori .minikube yang digunakan minikube untuk status/konfigurasi. Jika Anda menentukannya ke /path/to/somewhere dan di suatu tempat tidak sama dengan .minikube, akhirnya akan menjadi /path/to/somewhere/.minikube. Defaultnya adalah ~/.minikube jika tidak ditentukan. Harap diperhatikan: ini hanya digunakan oleh minikube dan tidak memengaruhi apa pun yang terkait dengan tool Kubernetes seperti kubectl.
-MINIKUBE_IN_STYLE - (bool) manually sets whether or not emoji and colors should appear in minikube. Set to false or 0 to disable this feature, true or 1 to force it to be turned on.
+* MINIKUBE_IN_STYLE - (bool) mengatur secara manual apakah emoji dan warna akan muncul di minikube atau tidak. Set ke false atau 0 untuk menonaktifkan fitur ini, true atau 1 untuk mengaktifkannya secara paksa.
-CHANGE_MINIKUBE_NONE_USER - (bool) automatically change ownership of ~/.minikube to the value of $SUDO_USER
+* CHANGE_MINIKUBE_NONE_USER - (bool) secara otomatis mengubah kepemilikan ~/.minikube ke nilai $SUDO_USER
-MINIKUBE_ENABLE_PROFILING - (int, 1 enables it) enables trace profiling to be generated for minikube
+* MINIKUBE_ENABLE_PROFILING - (int, 1 mengaktifkannya) memungkinkan pembuatan profil jejak untuk minikube
-MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE - (bool) suppresses Docker performance warnings when Docker is slow
+* MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE - (bool) menekan/surpress warning performance Docker saat Docker lambat
   export MINIKUBE_IN_STYLE=false
   minikube start

@@ Line 47: / Line 47: @@
   minikube start --feature-gates=EphemeralContainers=true
-==Modifying Kubernetes defaults==
+==Modifikasi Kubernetes default==
-The kubeadm bootstrapper can be configured by the --extra-config flag on the minikube start command. It takes a string of the form component.key=value where component is one of the strings
+Bootstrapper kubeadm dapat dikonfigurasi dengan flag --extra-config pada perintah minikube start. Dibutuhkan string dalam bentuk component.key=value di mana komponen adalah salah satu string
-kubeadm
+* kubeadm
-kubelet
+* kubelet
-apiserver
+* apiserver
-controller-manager
+* controller-manager
-scheduler
+* scheduler
-and key=value is a flag=value pair for the component being configured. For example,
   minikube start --extra-config=apiserver.v=10 --extra-config=kubelet.max-pods=100
-For instance, to allow Kubernetes to launch on an unsupported Docker release:
+Misalnya, untuk mengizinkan Kubernetes diluncurkan pada rilis Docker yang tidak didukung:
   minikube start --extra-config=kubeadm.ignore-preflight-errors=SystemVerification
-Runtime configuration
+==Konfigurasi Runtime configuration==
-The default container runtime in minikube varies. You can select one explicitly by using:
   minikube start --container-runtime=docker
-Options available are:
+Option yang tersedia adalah:
-containerd
+==Environment variable==
 minikube supports passing environment variables instead of flags for every value listed in minikube config. This is done by passing an environment variable with the prefix MINIKUBE_.
 For example the minikube start --iso-url="$ISO_URL" flag can also be set by setting the MINIKUBE_ISO_URL="$ISO_URL" environment variable.
-Exclusive environment tunings
+==Exclusive environment tuning==
 Some features can only be accessed by minikube specific environment variables, here is a list of these features:
 MINIKUBE_HOME - (string) sets the path for the .minikube directory that minikube uses for state/configuration. If you specify it to /path/to/somewhere and somewhere is not equal to .minikube, the final MINIKUBE_HOME will be /path/to/somewhere/.minikube. Defaults to ~/.minikube if unspecified. Please note: this is used only by minikube and does not affect anything related to Kubernetes tools such as kubectl.
 MINIKUBE_IN_STYLE - (bool) manually sets whether or not emoji and colors should appear in minikube. Set to false or 0 to disable this feature, true or 1 to force it to be turned on.
 CHANGE_MINIKUBE_NONE_USER - (bool) automatically change ownership of ~/.minikube to the value of $SUDO_USER
 MINIKUBE_ENABLE_PROFILING - (int, 1 enables it) enables trace profiling to be generated for minikube
 MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE - (bool) suppresses Docker performance warnings when Docker is slow
@@ Line 98: / Line 99: @@
 macOS
 Windows
-export MINIKUBE_IN_STYLE=false
+ export MINIKUBE_IN_STYLE=false
-minikube start
+ minikube start
 Making environment values persistent
 To make the exported variables persistent across reboots:
-Linux and macOS: Add these declarations to ~/.bashrc or wherever your shells environment variables are stored.
+* Linux and macOS: Add these declarations to ~/.bashrc or wherever your shells environment variables are stored.
-Windows: Either add these declarations to your ~\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 or run the following in a PowerShell terminal:
+* Windows: Either add these declarations to your ~\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 or run the following in a PowerShell terminal:
 [Environment]::SetEnvironmentVariable("key", "value", [EnvironmentVariableTarget]::User)
 ==Referensi==

@@ Line 37: / Line 37: @@
   minikube start --kubernetes-version=v1.11.10
-minikube follows the Kubernetes Version and Version Skew Support Policy, so we guarantee support for the latest build for the last 3 minor Kubernetes releases. When practical, minikube aims to support older releases as well so that users can emulate legacy environments.
+minikube mengikuti Kebijakan Dukungan Kubernetes Version dan Version Skew, jadi kami menjamin dukungan untuk build terbaru untuk 3 rilis minor Kubernetes terakhir. Jika memungkinkan, minikube bertujuan untuk mendukung rilis yang lebih lama juga sehingga pengguna dapat meniru lingkungan lawas.
-For up to date information on supported versions, see OldestKubernetesVersion and NewestKubernetesVersion in constants.go
+Untuk informasi terkini tentang versi yang didukung, lihat OldestKubernetesVersion dan NewestKubernetesVersion di constants.go https://github.com/kubernetes/minikube/blob/master/pkg/minikube/constants/constants.go
-Enabling feature gates
+==Enable feature-gates==
-Kubernetes alpha/experimental features can be enabled or disabled by the --feature-gates flag on the minikube start command. It takes a string of the form key=value where key is the component name and value is the status of it.
   minikube start --feature-gates=EphemeralContainers=true

@@ Line 31: / Line 31: @@
-==Selecting a Kubernetes version==
+==Memilih versi Kubernetes==
-By default, minikube installs the latest stable version of Kubernetes that was available at the time of the minikube release. You may select a different Kubernetes release by using the --kubernetes-version flag, for example:
+Secara default, minikube menginstal Kubernetes versi stabil terbaru yang tersedia pada saat rilis minikube. Anda dapat memilih rilis Kubernetes yang berbeda dengan menggunakan flag --kubernetes-version, misalnya:
   minikube start --kubernetes-version=v1.11.10
@@ Line 45: / Line 45: @@
   minikube start --feature-gates=EphemeralContainers=true
 Modifying Kubernetes defaults
 The kubeadm bootstrapper can be configured by the --extra-config flag on the minikube start command. It takes a string of the form component.key=value where component is one of the strings

@@ Line 10: / Line 10: @@
   minikube start --help
-==Persistent Configuration==
+==Konfigurasi Persistent==
-minikube allows users to persistently store new default values to be used across all profiles, using the minikube config command. This is done providing a property name, and a property value.
+minikube memungkinkan pengguna untuk dapat menyimpan nilai default baru untuk digunakan di semua profil, menggunakan perintah minikube config. Ini dilakukan dengan memberikan nama properti, dan nilai properti.
+Misalnya, untuk terus mengonfigurasi minikube untuk menggunakan hyperkit:
   minikube config set driver hyperkit
-You can get a complete list of configurable fields using:
+Anda bisa mendapatkan daftar lengkap field yang dapat dikonfigurasi menggunakan:
   minikube config --help
-To get a list of the currently set config properties:
+Untuk mendapatkan daftar properti konfigurasi yang saat ini ditetapkan:
   minikube config view
-Kubernetes configuration
+==Konfigurasi Kubernetes==
-minikube allows users to configure the Kubernetes components with arbitrary values. To use this feature, you can use the --extra-config flag on the minikube start command.
-This flag is repeated, so you can pass it several times with several different values to set multiple options.
+==Selecting a Kubernetes version==
 By default, minikube installs the latest stable version of Kubernetes that was available at the time of the minikube release. You may select a different Kubernetes release by using the --kubernetes-version flag, for example:
@@ Line 102: / Line 103: @@
 Windows: Either add these declarations to your ~\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 or run the following in a PowerShell terminal:
 [Environment]::SetEnvironmentVariable("key", "value", [EnvironmentVariableTarget]::User)
 ==Referensi==