-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent terminology for microk8s cloud #3517
Comments
Thanks for your comments! Some line-by-line replies below. Overall, I think the information is all there but I agree that its discovery could be better. I've made some updates. More to come. Thanks again!
That doc could indeed be clearer. And it shouldn't reference the commands -- that's something a user should (and can, in fact) get from our how-to guides (e.g., https://juju.is/docs/juju/manage-clouds#heading--add-a-cloud clearly distinguishes between the two cases).
From what I can see, it does. However, the way it does may be confusing as it lists in the same breath public clouds, Kubernetes, and private clouds, but that's not necessarily the right classification (because you can have Kubernetes on public clouds -- it's orthogonal to that).
I do not see that in the current version of the doc...
That doc left it implicit which cloud was which (essentially, all the Kubernetes clouds have Kubernetes in their name in some fashion -- EKS, AKS, GKE, MicroK8s). I've updated it now to say that explicitly: https://juju.is/docs/juju/juju-supported-clouds The fact that
Because it is true for any of the supported clouds that are Kubernets clouds, and MicroK8s is one of them. The fact that Juju automatically defines a cloud with the name |
I was trying to
add-cloud
a microk8s cloud, which led me through the following path:add-cloud
+add-credentials
vs.add-k8s
.add-cloud
can be used for microk8s.add-k8s
doc doesn't mention the "microk8s cloud".The text was updated successfully, but these errors were encountered: