c-managed-talos-lab-rma-0 Kubeconfig
[download]apiVersion: "v1"
clusters:
- cluster:
certificate-authority-data: "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUJpakNDQVMrZ0F3SUJBZ0lRWXFtaU1DbkpMUHpQSFdEZlhkTmNFakFLQmdncWhrak9QUVFEQWpBVk1STXcKRVFZRFZRUUtFd3ByZFdKbGNtNWxkR1Z6TUI0WERUSTJNRGt4T0RFek5USTBNbG9YRFRNMk1Ea3hOVEV6TlRJMApNbG93RlRFVE1CRUdBMVVFQ2hNS2EzVmlaWEp1WlhSbGN6QlpNQk1HQnlxR1NNNDlBZ0VHQ0NxR1NNNDlBd0VICkEwSUFCSFRwTHhPUmFiYTRKSUlHZS94MVVscFE1NkpSZUpFUnVYd1N4NnpVbC9aVzVJcFFoTnhYd1A4dmRqRlYKZDVQVlI0RnUwVHB3ekEwdFd4U3craGRPU2I2allUQmZNQTRHQTFVZER3RUIvd1FFQXdJQ2hEQWRCZ05WSFNVRQpGakFVQmdnckJnRUZCUWNEQVFZSUt3WUJCUVVIQXdJd0R3WURWUjBUQVFIL0JBVXdBd0VCL3pBZEJnTlZIUTRFCkZnUVV4VGZMZmdOMFZrZnlNS0lMZzVQbTI5aXp4OVF3Q2dZSUtvWkl6ajBFQXdJRFNRQXdSZ0loQU1NTkVRanYKdFRJT1NyZ3Bya0lhOUpIRjV5bHNDYUJiT1dhLy9YUWZyU2pXQWlFQW9oMnlsbEY2MUlmZjV0cGJIU3FsQ1crQwo0R1YwUzNrMXcvd01weXdadkxrPQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg=="
server: "https://api.c-managed-talos-lab-rma-0.vshnmanaged.net:6443"
name: "c-managed-talos-lab-rma-0"
contexts:
- context:
cluster: "c-managed-talos-lab-rma-0"
user: "oidc"
name: "oidc@c-managed-talos-lab-rma-0"
current-context: "oidc@c-managed-talos-lab-rma-0"
kind: "Config"
users:
- name: "oidc"
user:
exec:
apiVersion: "client.authentication.k8s.io/v1beta1"
args:
- "oidc-login"
- "get-token"
- "--oidc-issuer-url=https://id.vshn.net/auth/realms/vshn-realm"
- "--oidc-client-id=appuio-managed_c-managed-talos-lab-rma-0"
- "--oidc-extra-scope=email offline_access profile openid"
command: "kubectl"
interactiveMode: "IfAvailable"
provideClusterInfo: false
First time setup
- Make sure you have a recent
kubectl installed. See the upstream docs for install instructions.
- Download the
kubectl kubelogin plugin and ensure it’s available in your $PATH as kubectl-oidc_login
- Verify that the plugin is available.
kubectl oidc-login --version
- Download this cluster’s kubeconfig
- Set the
$KUBECONFIG environment variable
export KUBECONFIG=~/Downloads/c-managed-talos-lab-rma-0.kubeconfig
- Test access
kubectl auth whoami
If everything is setup correctly, this should authenticate you with your VSHN account in your browser and then show some details about your user.