Minikube: akses apps - Revision history

Unknown user: /* Access to ports <1024 on Windows requires root permission */

2023-05-08T01:51:20Z

Access to ports <1024 on Windows requires root permission

← Older revision		Revision as of 01:51, 8 May 2023
Line 143:		Line 143:
	https://superuser.com/questions/1328452/sudoers-nopasswd-for-single-executable-but-allowing-others		https://superuser.com/questions/1328452/sudoers-nopasswd-for-single-executable-but-allowing-others

	===~~Access to ports~~ <1024 on Windows ~~requires~~ root ~~permission~~===		===Akses ke port <1024 di Windows memerlukan izin root===

	~~If you are using~~ Docker ~~driver on~~ Windows, ~~there is a chance that you have an old version of~~ SSH ~~client you might get an error like~~ - ~~Privileged ports can only be forwarded by~~ root. ~~or you might not be able to access the service even after~~ minikube tunnel ~~if the access~~ port ~~is less than~~ 1024 ~~but for ports greater than~~ 1024 ~~works fine~~.		Jika Anda menggunakan driver Docker di Windows, ada kemungkinan Anda memiliki klien SSH versi lama, Anda mungkin mendapatkan kesalahan seperti - Port istimewa hanya dapat di-forward oleh root. atau Anda mungkin tidak dapat mengakses layanan bahkan setelah diberikan perintah minikube tunnel jika port akses <1024 tetapi untuk port >1024 berfungsi dengan baik.

	~~In order to resolve this~~, ~~ensure that you are running the latest version of~~ SSH ~~client~~. ~~You can install the latest version of the~~ SSH ~~client on~~ Windows ~~by running the following in a~~ Command Prompt ~~with an~~ Administrator ~~Privileges~~ (~~Requires chocolatey package manager~~)		Untuk mengatasi ini, pastikan Anda menjalankan klien SSH versi terbaru. Anda dapat menginstal versi terbaru klien SSH di Windows dengan menjalankan perintah berikut di Command Prompt dengan Hak Istimewa Administrator (Memerlukan manajer paket coklat)

	choco ~~install~~ openssh		choco instal openssh

	~~The latest version~~ (OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5) ~~which is available on~~ Windows 10 by default ~~doesn’t work~~. ~~You can track the issue with this over here~~ - https://github.com/PowerShell/Win32-OpenSSH/issues/1693		Versi terbaru (OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5) yang tersedia di Windows 10 secara default tidak berfungsi. Anda dapat melacak masalah dengan ini di - https://github.com/PowerShell/Win32-OpenSSH/issues/1693

	==Referensi==		==Referensi==

Unknown user: /* Avoiding password prompts */

2023-05-08T01:48:40Z

Avoiding password prompts

← Older revision		Revision as of 01:48, 8 May 2023
Line 137:		Line 137:
	CATATAN: --cleanup flag mempunyai nilai default true.		CATATAN: --cleanup flag mempunyai nilai default true.

	===~~Avoiding~~ password ~~prompts~~===		===Menghindari permintaan password===
	~~Adding a route requires~~ root ~~privileges for the user~~, ~~and thus there are differences in how to run~~ minikube tunnel ~~depending on the~~ OS. ~~If you want to avoid entering the~~ root ~~password~~, ~~consider setting~~ NOPASSWD ~~for “ip” and “route” commands~~:
			Menambahkan rute memerlukan hak akses root untuk pengguna, dan dengan demikian ada perbedaan dalam cara menjalankan minikube tunnel tergantung pada OS. Jika Anda ingin menghindari memasukkan password root, pertimbangkan untuk menset NOPASSWD untuk perintah "ip" dan "route":

	https://superuser.com/questions/1328452/sudoers-nopasswd-for-single-executable-but-allowing-others		https://superuser.com/questions/1328452/sudoers-nopasswd-for-single-executable-but-allowing-others

Unknown user: /* Cleaning up orphaned routes */

2023-05-08T01:46:38Z

Cleaning up orphaned routes

← Older revision		Revision as of 01:46, 8 May 2023
Line 129:		Line 129:
	CATATAN: driver docker tidak mendukung resolusi DNS		CATATAN: driver docker tidak mendukung resolusi DNS

	===~~Cleaning up orphaned routes~~===		===Membersihkan route yang menggantung===
	If the minikube tunnel shuts down in an abrupt manner, it may leave orphaned network routes on your system. If this happens, the ~/.minikube/tunnels.json file will contain an entry for that tunnel. To remove orphaned routes, run:

	minikube tunnel -~~-cleanup~~		Jika minikube tunnel mati secara tiba-tiba, itu mungkin meninggalkan rute jaringan tanpa induk di sistem Anda. Jika ini terjadi, file ~/.minikube/tunnels.json akan berisi entri untuk tunnel tersebut. Untuk menghapus rute yang menggantung, jalankan:

	~~NOTE~~: --cleanup ~~flag’s~~ default ~~value is~~ true.		minikube tunnel --cleanup

			CATATAN: --cleanup flag mempunyai nilai default true.

	===Avoiding password prompts===		===Avoiding password prompts===

Unknown user: /* DNS resolution (experimental) */

2023-05-08T01:42:39Z

DNS resolution (experimental)

← Older revision		Revision as of 01:42, 8 May 2023
Line 124:		Line 124:

	===DNS resolution (experimental)===		===DNS resolution (experimental)===
	~~If you are on macOS, the tunnel command also allows DNS resolution for Kubernetes services from the host.~~

	~~NOTE~~: docker ~~driver doesn’t support~~ DNS ~~resolution~~		Jika kita menggunakan macOS, perintah tunnel juga memungkinkan resolusi DNS untuk service Kubernetes dari host.

			CATATAN: driver docker tidak mendukung resolusi DNS

	===Cleaning up orphaned routes===		===Cleaning up orphaned routes===

Unknown user: /* Example of LoadBalancer */

2023-05-08T01:41:03Z

Example of LoadBalancer

← Older revision		Revision as of 01:41, 8 May 2023
Line 89:		Line 89:
	Service bertipe LoadBalancer dapat diakses melalui perintah minikube tunnel. Itu harus dijalankan di window terminal terpisah agar LoadBalancer tetap berjalan. Ctrl-C di terminal dapat digunakan untuk menghentikan proses saat rute jaringan akan di clear up.		Service bertipe LoadBalancer dapat diakses melalui perintah minikube tunnel. Itu harus dijalankan di window terminal terpisah agar LoadBalancer tetap berjalan. Ctrl-C di terminal dapat digunakan untuk menghentikan proses saat rute jaringan akan di clear up.

	===~~Example of~~ LoadBalancer===		===Contoh LoadBalancer===
	~~Run the tunnel in a separate terminal~~

	~~It will ask for a~~ password.		Jalankan tunnel di terminal terpisah
			Itu akan meminta password.

	minikube tunnel		minikube tunnel

	minikube tunnel ~~runs as a process~~, ~~creating a network route on the~~ host ~~to the service~~ CIDR ~~of the~~ cluster ~~using the cluster’s~~ IP ~~address as a~~ gateway. ~~The~~ tunnel ~~command exposes the external~~ IP ~~directly to any~~ program ~~running on the~~ host ~~operating system~~.		minikube tunnel berjalan sebagai sebuah proses, membuat rute jaringan pada host ke layanan CIDR cluster menggunakan alamat IP cluster sebagai gateway. Perintah tunnel membuka IP eksternal langsung ke program apa pun yang berjalan di sistem operasi host.

	tunnel output ~~example~~
	~~Create a~~ Kubernetes deployment		====contoh tunnel output====
			Membuat Kubernetes deployment

	kubectl create deployment hello-minikube1 --image=kicbase/echo-server:1.0		kubectl create deployment hello-minikube1 --image=kicbase/echo-server:1.0

	~~Create a~~ Kubernetes service ~~with~~ type LoadBalancer		Membuat Kubernetes service dengan type LoadBalancer

	kubectl expose deployment hello-minikube1 --type=LoadBalancer --port=8080		kubectl expose deployment hello-minikube1 --type=LoadBalancer --port=8080

	~~Check the~~ external IP		Cek external IP

	kubectl get svc		kubectl get svc
Line 114:		Line 115:
	hello-minikube1 LoadBalancer 10.96.184.178 10.96.184.178 8080:30791/TCP 40s		hello-minikube1 LoadBalancer 10.96.184.178 10.96.184.178 8080:30791/TCP 40s

	~~Note that without~~ minikube tunnel, Kubernetes ~~will show the~~ external IP as “pending”.		Catatan tanpa minikube tunnel, Kubernetes akan memperlihatkan external IP sebagai “pending”.

	~~Try in your browser~~

	~~Open in your~~ browser (~~ensure there is no proxy set~~)		Coba di Browser. Bukan browser (pastikan tidak ada proxt)

	http://REPLACE_WITH_EXTERNAL_IP:8080		http://REPLACE_WITH_EXTERNAL_IP:8080

	~~Each service will get its own~~ external IP.		Setiap layanan akan memperoleh external IP masing-masing.

	===DNS resolution (experimental)===		===DNS resolution (experimental)===

Unknown user: /* Menggunakan minikube tunnel */

2023-05-08T01:32:34Z

Menggunakan minikube tunnel

← Older revision		Revision as of 01:32, 8 May 2023
Line 87:		Line 87:
	===Menggunakan minikube tunnel===		===Menggunakan minikube tunnel===

	~~Services of type~~ LoadBalancer ~~can be exposed via the~~ minikube tunnel ~~command~~. ~~It must be run in a separate~~ terminal ~~window to keep the~~ LoadBalancer ~~running~~. Ctrl-C ~~in the~~ terminal ~~can be used to terminate the process at which time the network routes will be cleaned~~ up.		Service bertipe LoadBalancer dapat diakses melalui perintah minikube tunnel. Itu harus dijalankan di window terminal terpisah agar LoadBalancer tetap berjalan. Ctrl-C di terminal dapat digunakan untuk menghentikan proses saat rute jaringan akan di clear up.

	===Example of LoadBalancer===		===Example of LoadBalancer===

Unknown user: /* LoadBalancer access */

2023-05-08T00:21:02Z

LoadBalancer access

← Older revision		Revision as of 00:21, 8 May 2023
Line 82:		Line 82:

	==LoadBalancer access==		==LoadBalancer access==
	~~A LoadBalancer service is the standard way to expose a service to the internet. With this method, each service gets its own IP address.~~

	===~~Using~~ minikube tunnel===		LoadBalancer service adalah cara standar untuk memexpose service ke internet. Dengan metode ini, setiap service mendapatkan IP address-nya sendiri.

			===Menggunakan minikube tunnel===

	Services of type LoadBalancer can be exposed via the minikube tunnel command. It must be run in a separate terminal window to keep the LoadBalancer running. Ctrl-C in the terminal can be used to terminate the process at which time the network routes will be cleaned up.		Services of type LoadBalancer can be exposed via the minikube tunnel command. It must be run in a separate terminal window to keep the LoadBalancer running. Ctrl-C in the terminal can be used to terminate the process at which time the network routes will be cleaned up.

Line 148:		Line 150:

	The latest version (OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5) which is available on Windows 10 by default doesn’t work. You can track the issue with this over here - https://github.com/PowerShell/Win32-OpenSSH/issues/1693		The latest version (OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5) which is available on Windows 10 by default doesn’t work. You can track the issue with this over here - https://github.com/PowerShell/Win32-OpenSSH/issues/1693




	==Referensi==		==Referensi==

Unknown user: /* Increasing the NodePort range */

2023-05-07T23:03:05Z

Increasing the NodePort range

← Older revision		Revision as of 23:03, 7 May 2023
Line 73:		Line 73:
	kubectl get service <service-name> --output='jsonpath="{.spec.ports[0].nodePort}"'		kubectl get service <service-name> --output='jsonpath="{.spec.ports[0].nodePort}"'

	===~~Increasing the~~ NodePort range===		===Meningkatkan NodePort range===
	By default, minikube ~~only exposes ports~~ 30000-32767. ~~If this does not work for you~~, ~~you can adjust the~~ range ~~by using~~:
			Secara default, minikube hanya membuka port 30000-32767. Jika ini tidak berhasil, kita dapat menyesuaikan range dengan menggunakan:

	minikube start --extra-config=apiserver.service-node-port-range=1-65535		minikube start --extra-config=apiserver.service-node-port-range=1-65535

	~~This flag also accepts a comma separated list of ports and~~ port ~~ranges~~.		Flag ini juga menerima daftar port dan range port yang dipisahkan koma.

	==LoadBalancer access==		==LoadBalancer access==

Unknown user: /* Getting the NodePort using kubectl */

2023-05-07T23:00:38Z

Getting the NodePort using kubectl

← Older revision		Revision as of 23:00, 7 May 2023
Line 66:		Line 66:
	http://127.0.0.1:TUNNEL_PORT		http://127.0.0.1:TUNNEL_PORT

	===~~Getting the~~ NodePort ~~using~~ kubectl===		===Mendapatkan NodePort menggunakan kubectl===
	The minikube VM is exposed to the host system via a host-only IP address, that can be obtained with the minikube ip command. Any services of type NodePort can be accessed over that IP address, on the NodePort.

	~~To determine the~~ NodePort ~~for your service~~, ~~you can use a~~ kubectl ~~command like this~~ (~~note that~~ nodePort ~~begins with lowercase~~ n in JSON ~~output~~):		VM minikube diekspos ke sistem host melalui alamat IP host-only, yang dapat diperoleh dengan perintah ip minikube. Semua layanan bertipe NodePort dapat diakses melalui alamat IP tersebut, di NodePort.
			Untuk menentukan NodePort untuk layanan kita, kita dapat menggunakan perintah kubectl seperti ini (perhatikan bahwa nodePort dimulai dengan huruf kecil n di keluaran JSON):

	kubectl get service <service-name> --output='jsonpath="{.spec.ports[0].nodePort}"'		kubectl get service <service-name> --output='jsonpath="{.spec.ports[0].nodePort}"'

Unknown user: /* Contoh NodePort */

2023-05-07T22:56:25Z

Contoh NodePort

← Older revision		Revision as of 22:56, 7 May 2023
Line 35:		Line 35:
	===Contoh NodePort===		===Contoh NodePort===

	~~Create a~~ Kubernetes deployment		Membuat Kubernetes deployment

	kubectl create deployment hello-minikube1 --image=kicbase/echo-server:1.0		kubectl create deployment hello-minikube1 --image=kicbase/echo-server:1.0

	~~Create a~~ Kubernetes service type NodePort		Membuat Kubernetes service type NodePort

	kubectl expose deployment hello-minikube1 --type=NodePort --port=8080		kubectl expose deployment hello-minikube1 --type=NodePort --port=8080

	~~Check~~ Node Port		Cek Node Port

	$ kubectl get svc		$ kubectl get svc
Line 52:		Line 52:

	minikube service hello-minikube1 --url		minikube service hello-minikube1 --url
	~~minikube service hello-minikube1 --url runs as a process, creating a tunnel to the cluster. The command exposes the service directly to any program running on the host operating system.~~

	service output ~~example~~		minikube service hello-minikube1 --url run sebagai proses, membuat tunnel ke cluster. Perintah tersebut membuka service secara langsung ke program apapun yang jalan di sistem operasi host.
	~~Check~~ ssh tunnel ~~in another~~ terminal
			====contoh service output====

			Cek ssh tunnel di terminal lain

	$ ps -ef \| grep docker@127.0.0.1		$ ps -ef \| grep docker@127.0.0.1
	ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -N docker@127.0.0.1 -p 55972 -i /Users/FOO/.minikube/machines/minikube/id_rsa -L TUNNEL_PORT:CLUSTER_IP:TARGET_PORT		ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -N docker@127.0.0.1 -p 55972 -i /Users/FOO/.minikube/machines/minikube/id_rsa -L TUNNEL_PORT:CLUSTER_IP:TARGET_PORT

	~~Try in your~~ browser		Coba menggunakan browser. Buka di browser pastikan tidak ada proxy yang di set,

	~~Open in your~~ browser ~~(ensure there is no~~ proxy set)

	http://127.0.0.1:TUNNEL_PORT		http://127.0.0.1:TUNNEL_PORT