If you enable the dashboard on a microk8s cluster (or single node) you can follow this tutorial: https://microk8s.io/docs/addon-dashboard
The problem is, the command
microk8s kubectl port-forward -n kube-system service/kubernetes-dashboard 10443:443
has to be reexecuted every time you restart your node, which you use to access the dashboard.
A better configuration can be done this way: Run the following command and change
type: ClusterIP --> type: NodePort
kubectl -n kube-system edit service kubernetes-dashboard
# Please edit the object below. Lines beginning with a '#' will be ignored,Then run
# and an empty file will abort the edit. If an error occurs while saving this file will be
# reopened with the relevant failures.
#
apiVersion: v1
kind: Service
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"labels":{"k8s-app":"kubernetes-dashboard"},"name":"kubernetes-dashboard","namespace":"kube-system"},"spec":{"ports":[{"port":443,"targetPort":8443}],"selector":{"k8s-app":"kubernetes-dashboard"}}}
creationTimestamp: "2021-01-22T21:19:24Z"
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard
namespace: kube-system
resourceVersion: "3599"
selfLink: /api/v1/namespaces/kube-system/services/kubernetes-dashboard
uid: 19496d44-c454-4f55-967c-432504e0401b
spec:
clusterIP: 10.152.183.81
clusterIPs:
- 10.152.183.81
ports:
- port: 443
protocol: TCP
targetPort: 8443
selector:
k8s-app: kubernetes-dashboard
sessionAffinity: None
type: ClusterIP
status:
loadBalancer: {}
root@ubuntu:/home/ubuntu# kubectl -n kube-system get service kubernetes-dashboard
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes-dashboard NodePort 10.152.183.81 <none> 443:30713/TCP 4m14s
After that you can access the dashboard over the port which is given behind the 443: - in my case https://zigbee:30713
No comments:
Post a Comment