Closed planetf1 closed 2 years ago
The 'insure' WARNING is from an out of the box install of microk8s ...
Rancher Desktop can also be added to the list for Windows users (perhaps mac too)
Install from https://rancherdesktop.io/
This also has explicit WSL integration, so may be a simpler/easier fit for hybrid work, ie when developing a connector under WSL2 & running it alongside Egeria running under k8s
Rancher desktop adds 'kubectl' and 'helm' to the standard path during install
As such the usual commands used for linux/macos works just fine
Overall rancher desktop is more complete, more integrated, has GUI, supports pod metrics (top pods/nodes for example) However on the downside the default config took 12GB on my 16GB machine -- and we may have users with 8GB machines running dojo/demos. Need to understand if configurable It also seems to run with a higher background level of CPU vs microk8s. It seems to run everything under WSL- beyond the GUI (whilst microk8s uses a slightly more conventional VM setup) So whilst overall it may be better, there is some risk in going down this route for Dojo However for egeria, it works....
these docs were updated (simply point to the official docs) for the dojo. closing.
The instructions for setting up microk8s on windows at https://odpi.github.io/egeria-docs/guides/operations/kubernetes/k8s/ refer the user to the official windows instructions.
Whilst that's initially appropriate -- to download and run the GUI installer, it then needs to be more explicit.
Following install/reboot the same instructions are used as for macOS (so this can be common) ie
A few other observations:
ON Helm....
A caveat is noted at https://odpi.github.io/egeria-docs/guides/operations/kubernetes/helm/ that the user needs to use 'microk8s.kubectl' or 'microk8s.helm'. This is non-standard. For the dojo we will explicitly use 'microk8s helm3 ....' but some users may still be confused by these joint instructions. An adominition, perhaps offering the variant may help as otherwise the user may pickup an old version or wrong version of helm, and for those new to k8s this could be confusing
And testing our charts - the instructions working ok on x86 windows 10