Versions Compared

Old Version 17

changes.mady.by.user Maurizio Montis

Saved on

compared with

New Version 18

changes.mady.by.user Andrea Michelotti

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

NOTE: the alias command should (must) be inserted under ~/.bashrc

...

You can verify the K3s installation by checking the POD status:

kubectl get pod -A

Retrieve Service CIDR

For further EPIK8s installation is important to take note of Service CIDR that is the interval range of internal service cluster IPs.


cat /var/snap/microk8s/current/args/kube-apiserver | 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.


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.

...