How to connect to a Cluster

We can just run the command

kubectl --kubeconfig="/home/den/Altenar/k8s/test_cluster.yml" get pods

with cluster config stored in test_cluster.yml file

Or we can modify cluster config stored in $HOME/.kube/config file

apiVersion: v1
clusters:
- cluster:
    certificate-authority: /home/den/.minikube/ca.crt
    server: https://192.168.99.100:8443
  name: minikube
contexts:
- context:
    cluster: minikube
    user: minikube
  name: minikube
current-context: minikube
kind: Config
preferences: {}
users:
- name: minikube
  user:
    client-certificate: /home/den/.minikube/client.crt
    client-key: /home/den/.minikube/client.key

apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSURDekNDQWZPZ0F3SUJBZ0lRSHROQjBMaEZsc1NhNUpHTFY1bzFXekFOQmdrcWhraUc5dzBCQVFzRkFEQXYKTVMwd0t3WURWUVFERXlRelpHTXpOakF3TWkxak5HSmlMVFJsTVRFdE9XTm1NeTA0TUdReU5HWXpOREE1WkRrdwpIaGNOTWpBd016QTJNVE14TURFNFdoY05NalV3TXpBMU1UUXhNREU0V2pBdk1TMHdLd1lEVlFRREV5UXpaR016Ck5qQXdNaTFqTkdKaUxUUmxNVEV0T1dObU15MDRNR1F5TkdZek5EQTVaRGt3Z2dFaU1BMEdDU3FHU0liM0RRRUIKQVFVQUE0SUJEd0F3Z2dFS0FvSUJBUURIQ1NFbnYwNG9SMndRK3gzZVVuQTZad0UvNmJyOGpSUGQ4TkJoNnkzegpmVktZUVp2dEFWS1NIU0xXZnp2OXJZQWxHOUo5SXhOa3NzSkVlRHpBS2tiNlp4TkZyTG55RDFmRUwwL1l5Y09hCkJQV1pTcGJwTVlaTUFDbFhXWld6TkliNXMvTVFORWhSNVFuTEtLcVJ6MlBmc2tXd1BGNjMrbURrU2lTTG4yTlEKZHF5QmhtcXZWeVBiSWpqQnFTcGw0Tk8yVE5SOWV3b1E2U1h2V20rWkwrcXlHWHpWT1BsTTQxWnJXdkVianZGSApuRUYwTTJRNU1hNHpOUDRJTUJyTCtKQU03RS9Rck5CQmJkV0lkdXNDUjRZMHQ4Y0JpRHhRays5WTltVEtwSGxZCnBEZDMxUnhscHhnZ2xIaTRmWVZBSlVKVWZOZnVSQStRVVdiZzJDbVMxQ01wQWdNQkFBR2pJekFoTUE0R0ExVWQKRHdFQi93UUVBd0lDQkRBUEJnTlZIUk1CQWY4RUJUQURBUUgvTUEwR0NTcUdTSWIzRFFFQkN3VUFBNElCQVFCeApqVHFrallUckU1bzZsZGFJVnM2eGNOeGFES2ZBWFVLd0IyMTIybG1VdlZkOTV3ZWtOeWFtRHY3Q3NHQjYwcW5ECjM4UXcwWkhaYTlSUDFCcGR6anBJZGFpSG4rdm1BN3NFLytLSms3ZVlZbWw4RzFuRGhSQjZrVG1Od3dNSTQvTVoKMmVCTDV2a216UFVMcTYyY3J0d1o0cFlEMXF5WUtBK0JNcGM2b3NEWGc0REl3Ukl4SHJqQ3M0VjRrelpBL3N5agpwbzluazYyNFA3R2l2Wld1ZXlvdllRSnFHRjRzcHh4dlVQNmdRbDdjcmdmS0VUVkpZbFo5bFhsVWtWTE40UGdwCmQyRkExLzdxR2orejdCdnQ4SXhHU2NYK2FoSzUxVUxPcHM5VFBsRldkQkFwYnliVkc3YlFaRm9vMzFYOFlQV1oKMzMzRUVOLzRMMTAvMnNSWEVsMloKLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo=
    server: https://35.187.70.82
  name: gke_altenar-dev-sbenvs_europe-west1_euwe1c1-gke000
contexts:
- context:
    cluster: gke_altenar-dev-sbenvs_europe-west1_euwe1c1-gke000
    namespace: test
    user: test-user
  name: gke_altenar-dev-sbenvs_europe-west1_euwe1c1-gke000
current-context: gke_altenar-dev-sbenvs_europe-west1_euwe1c1-gke000
kind: Config
preferences: {}
users:
- name: test-user
  user:
    token: eyJhbGciOiJSUzI1NiIsImtpZCI6IlV2bXVvR3NJS0tQU2JnMG84UFNxOUEzdXA0SEx1Y1FrdmtzUE42ZEVBNjgifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJ0ZXN0Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZWNyZXQubmFtZSI6InRlc3QtdXNlci10b2tlbi13cHZ2cyIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJ0ZXN0LXVzZXIiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiJkNjE1OWQ2YS1jNWRjLTQ0ZGUtOGFiYy01YzQ1NmMxZTM2OGEiLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6dGVzdDp0ZXN0LXVzZXIifQ.ab4ywvDQwrc6WTjkksAOWu8uaphY8xWOedd2lnBvAp2epN8MTt5_Dc2-LImUMHbvqPkkoSKkYwRS4uQ-vUGcOLT33DDyxI6hSjLH9qqjd3BhcxhhJEL6M7F1CZ4f7YWSQtF-I8TW4-uwmEcqZB_nh0am7DwBrV7WDtysOFCW6YktPPFhxYUJLq7kh2-2UiEtLVgIqBI_C2EAxBy8pXlvce4m0n4R9yGoAHgEmofScjao4U2FnaP1FSPorv6_ubWi9R3qFyYFTfk2FwUIqyI_m-1twE4hJOBeNf7fxzg1CJArK5fkIrXzVVK7HJwWIVWXtK57PodkCLp2UI_iPEbnxA

to use the context we need to set the command and set the context name from the config file

After that we can check available contexts

NLAM0

kubectl config use-context nlam0-s002

Last updated