...
Explore the microk8s environment
You can verify the K3s microk8s installation by checking the node status:
kubectl get nodes
You can verify the K3s microk8s installation by checking the POD status:
...
cat /var/snap/microk8s/current/args/kube-apiserver | grep service-cluster-ip-range
or for kubernates vanilla
cat /etc/kubernetes/manifests/kube-apiserver.yaml|grep service-cluster-ip-range
This interval should be indicated to EPIK8s to instruct the range of IPs to give to pod services (because CA/PVA protocols dont support correctly dynamic DNS)
https://github.com/epics-base/epics-base/issues/488.
...
Metallb configuration
For further EPIK8s installation is important to take note of loadbalancer IP configured in the install process.
...
Some of this IP should be used to access internal EPIK8s service like cagateway and pvagateway.
To check the addresses already in use see the EXTERNAL-IP column:
kubectl get svc -o wide -A
Expose K8s Dashboard
You can expose the Dashboard using a NodePort, Ingress, or LoadBalancer service, depending on your setup. By default, it uses a ClusterIP, which is not accessible externally.
...