-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Rework Quick & Helm Installation Guide #15695
Conversation
275309a
to
09da4bf
Compare
This commit reworks the quick installation guides to use the Cilium CLI. This allows to completely remove the quick-install.yaml. The Helm installation guides are kept and moved into a new "Advanced Installation" section. This also allows to standardize the Observability instructions and move it into a single guide split into Setup, CLI, and UI. In order to really simplify, the only remaining guide that was using the cilium namespace for installation is also changed to use kube-system so all follow-up guides can be kept the same. Signed-off-by: Thomas Graf <thomas@cilium.io>
As we no longer depend on the various quick-install YAML files, we can remove all the logic to generate them. Signed-off-by: Thomas Graf <thomas@cilium.io>
09da4bf
to
01b8fee
Compare
01b8fee
to
d56ded7
Compare
|
||
.. tabs:: | ||
|
||
.. group-tab:: GKE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Nit] For consistency, we should rename tabs for GKE/AKS/EKS to include the platform names, as in the next set of tabs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unlike the tabs below, these are actually specific to GKE, EKS, AKS, and so on.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I'm not sure I follow 🤔
Does that mean there is a difference between the GKE tab highlighted above and the GCP/GKE tab present in the next set of tabs (line 134 in same file)?
.. group-tab:: GCP/GKE
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the "GKE" tab in create cluster is creating a GKE cluster. The "GCP/GKE" tab in "Install Cilium" will function for both GKE and self-managed clusters in GCP. I'm OK to also label GCP above if you think that's less confusing overall.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah I see! I think I got mostly confused by the fact the GCP/GKE
-like tabs explicitly only mention provider-managed clusters (e.g. Install Cilium into the GKE cluster:
), so I did not think the docs were targeting self-managed GCP clusters.
Perhaps we ought to rephrase some parts a bit differently for self-managed clusters.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, one optional minor comment on minikube target
cp "install/kubernetes/quick-install.yaml" /tmp/cilium-minikube.yaml | ||
|
||
sed -i 's|latest|dev|g' /tmp/cilium-minikube.yaml | ||
sed -i 's|docker.io/||g' /tmp/cilium-minikube.yaml | ||
sed -i 's|imagePullPolicy: Always|imagePullPolicy: Never|g' /tmp/cilium-minikube.yaml | ||
|
||
kubectl create -f /tmp/cilium-minikube.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of removing this script and the minikube target as there might be developers who depend on it (I'm not sure who though), maybe we can replace the highlighted lines with the cilium-cli?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've asked @mrostecki whether the script is still needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't use the script lately.
The question is if anyone finds it useful. If not, I'm fine with removing it. Otherwise can follow up with switching to cilium-cli in it.
Consolidate most separate installation guides covering Helm-based installation into a single guide with tabs for the different platforms. Some guides are left intact which are either quite special or relatively uncommon. Signed-off-by: Thomas Graf <thomas@cilium.io>
d56ded7
to
b6ec84c
Compare
You can install Cilium on any Kubernetes cluster. If you already have a | ||
Kubernetes cluster, skip this step. If you want to create a cluster, pick one | ||
of the options below: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just noticed the bit about skipping the step if a cluster is already available should probably be moved to the previous section.
Major rework of quick & helm install guides. Most guides are consolidated into two main ones.
Rendered preview:
https://deploy-preview-15695--cilium-doc.netlify.app/