This message was deleted.
# rke2a
adamant-kite-43734
07/25/2023, 3:03 PMThis message was deleted.
c
creamy-pencil-82913
07/25/2023, 5:14 PMFrom the quickstart page you linked:
• A kubeconfig file will be written toDid you want to./etc/rancher/rke2/rke2.yaml
export KUBECONFIG=/etc/rancher/rke2/rke2.yamlb
brainy-summer-72240
07/25/2023, 5:16 PMSorry if this is a stupid question, but I thought the kubeconfig that rke-server starts with would be based on the rke2.yaml anyways? rather than the other way around
c
creamy-pencil-82913
07/25/2023, 5:17 PMAre you confusing the rke2.yaml kubeconfig, and the config.yaml configuration file?
creamy-pencil-82913
07/25/2023, 5:18 PMThe admin kubeconfig at rke2.yaml is generated by RKE2 when it starts up. It won’t exist until the rke2-server service is started the first time.
b
brainy-summer-72240
07/25/2023, 5:23 PMI see, no I didn't want to export the kubeconfig before running rke2 as far as I'm aware
c
creamy-pencil-82913
07/25/2023, 5:30 PMyou don’t need to export that before running rke2
creamy-pencil-82913
07/25/2023, 5:30 PMjust before using the kubectl CLI, so it know where to find the kubeconfig. If you don’t do that, it will try to connect to kubernetes using plain-text on port 8080, which is why you got an error.
b
brainy-summer-72240
07/25/2023, 5:40 PMOh I see
brainy-summer-72240
07/25/2023, 5:41 PMthanks, that makes sense
brainy-summer-72240
07/25/2023, 5:41 PMSorry, a little bit out of my wheelhouse, I do a lot of TF and Ansible but I haven't configured my own k8s on prem before
brainy-summer-72240
07/26/2023, 12:24 PMI tried exporting KUBECONFIG to the rke.yaml but kubectl config view still shows an empty/default config, I read something about ~/.kube/config ?
brainy-summer-72240
07/26/2023, 12:36 PMnevermind, solved that issue by specifying kubeconfig in kubectl commands
6 Views