...
Right now we have the K8s cluster setup in offline mode on the client-server machine replicated in the lab. However, we see that support for the offline version is poor for v2.8.2 currently used by KUD. Setting up the galaxy requirement has been a blocker. We have developed an approach to it to get the add-ons going.
The current system in KuD has a lot of Ansible code that will be rewritten
Proposed workflow
- Have KuD live to run for August 15 release.
- September 15 Priorities
- Update the version of Kubespray from 2.8.2 to 2.11 to leverage the features of Kubespray caching available in Master.
- Test it on KuD-live version
- Have the new daemon sets integrated with the online version since, some of them require a higher version of Kubeadmn and kubectl version which is automatically updated once, kubespray is updated.
- Have the existing addons like virtlet, nfd, cmk, rook etc be converted into daemon sets and tested in live KuD for the addons converted into Daemonsets. This depends we should also have non-daemon sets to test out our infra.
- Provide OVN installation package information and OVN daemonset.yaml - Ritu?
- Have docker registry to have come container images to be pulled from the provisioned servers.
- October 15 Priorities
- Host on Http-server put packages for addons so that the add-on scripts are not manipulated (If any)
- Have all the docker images used by Kubespray to pull from here from deployment.
- Also, have ansible roles created which will help to maintain a single version of KuD for both online and offline deployment.