You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
looking for some help with my setup. I have an external application that needs to make an API call to my cluster. I'm currently running Microk8s v1.22.5-3+66632586920c77
I've added the token to the application and when I try to validate I get: "Failed to get Pods. Max retry exceeded. Error: SSL certificate error"
MicroK8s says that it consolidated a few services into daemon-kubelite
Used in release 1.21 and later. The kubelite daemon runs as subprocesses the scheduler, controller, proxy, kubelet, and apiserver services. Each of these individual services can be configured using arguments in the matching ${SNAP_DATA}/args/ directory:
- scheduler ${SNAP_DATA}/args/kube-scheduler
- controller ${SNAP_DATA}/args/kube-controller-manager
- proxy ${SNAP_DATA}/args/kube-proxy
- kubelet ${SNAP_DATA}/args/kubelet
- apiserver ${SNAP_DATA}/args/kube-apiserver
looking for some help with my setup. I have an external application that needs to make an API call to my cluster. I'm currently running Microk8s v1.22.5-3+66632586920c77
I have my API Server: https://10.10.40.11:16443
I've created a Service account:
I've added the token to the application and when I try to validate I get: "Failed to get Pods. Max retry exceeded. Error: SSL certificate error"
MicroK8s says that it consolidated a few services into daemon-kubelite
Also it seems like I'm using one of the approved K8s auth methods: https://kubernetes.io/docs/reference/access-authn-authz/authentication/#authentication-strategies
The app has me generate a Service Account:
$ k describe sa -n kube-system pan-plugin-user
which has a secret:
$ k describe secret -n kube-system pan-plugin-user-token-zr7xq
And then it generates a cred.json file:
kubectl -n kube-system get secrets -o json >> cred.json
So the file has the ca.crt in there, I feel like that should work for the auth
If I look at:
$ microk8s config
matches the one in the json file.
inspection-report-20220117_121858.tar.gz
The text was updated successfully, but these errors were encountered: