Please provide the motivation or use case for this enhancement:
Canonical is dropping microk8s in favor of k8s
Below is the output of sudo snap install --edge k8s --classic && k8s --help:
Canonical Kubernetes CLI
Usage:
k8s [command]
Available Commands:
bootstrap Bootstrap a new Kubernetes cluster
completion Generate the autocompletion script for the specified shell
config Generate a kubeconfig that can be used to access the Kubernetes cluster
disable Disable core cluster functionalities
enable Enable core cluster functionalities
get get cluster configuration
get-join-token Create a token for a node to join the cluster
help Help about any command
join-cluster Join a cluster using the provided token
kubectl Integrated Kubernetes kubectl client
remove-node Remove a node from the cluster
set Set cluster configuration
status Retrieve the current status of the cluster
Flags:
-h, --help help for k8s
-o, --output-format string set the output format to one of plain, json or yaml (default "plain")
-t, --timeout duration the max time to wait for the command to execute (default 1m30s)
Use "k8s [command] --help" for more information about a command.
How can we best workaround this issue so far?
No response
How would you approach solving this problem within CNDI?
No response
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Version
cndi v2.4.5 kubeseal v0.26.0 terraform v1.5.5
Please provide a summary of the enhancement you are proposing:
Replace
microk8s
distribution with Canonical's newk8s
distribution.https://snapcraft.io/k8s
Please provide the motivation or use case for this enhancement:
Canonical is dropping
microk8s
in favor ofk8s
Below is the output of
sudo snap install --edge k8s --classic && k8s --help
:How can we best workaround this issue so far?
No response
How would you approach solving this problem within CNDI?
No response
Code of Conduct