Skip to content
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.

Sign up for GitHub

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

docs: update deploying cilium docs for v1.8 #9034

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

docs: update deploying cilium docs for v1.8 #9034

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f554969
docs: update deploying cilium docs for v1.8
ChickenIQ Jul 18, 2024
9e27504
Merge branch 'siderolabs:main' into main
ChickenIQ Jul 31, 2024
31bc370
Add namespace to install command
ChickenIQ Jul 31, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions website/content/v1.8/kubernetes-guides/network/deploying-cilium.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -347,7 +347,7 @@ We can leverage this to our advantage to install Cilium by using an inline manif
hostNetwork: true
containers:
- name: cilium-install
image: quay.io/cilium/cilium-cli-ci:latest
image: alpine/helm:latest
env:
- name: KUBERNETES_SERVICE_HOST
valueFrom:
Expand All @@ -357,8 +357,11 @@ We can leverage this to our advantage to install Cilium by using an inline manif
- name: KUBERNETES_SERVICE_PORT
value: "6443"
command:
- cilium
- helm
- install
- cilium
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it a typo or should it be two times?

I would want some input from @leppeK on this change, as he brought this change initially

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe it is correct.
helm install [NAME] [CHART] [flags]

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For helm it is correct, unfortunately helm leaves traces of the release which you might not want.

I'll see if I can convince Cilium to provide an official container image for all platforms

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the comments already indicate that you can use this method to do anything, if you want to use this to install something else using helm or whatever it works as well.

A use case could be installing your CNI and/or ArgoCD at bootstrap time

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't it the same as manually installing using helm after bootstrap?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doing stuff at bootstrap means you can do it completely declaratively and in one go and at the right time... Great for reproducibilty

- cilium
- --repo=https://helm.cilium.io/
- --set ipam.mode=kubernetes
- --set kubeProxyReplacement=true
- --set securityContext.capabilities.ciliumAgent="{CHOWN,KILL,NET_ADMIN,NET_RAW,IPC_LOCK,SYS_ADMIN,SYS_RESOURCE,DAC_OVERRIDE,FOWNER,SETGID,SETUID}"
Expand Down