https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
l
I find it more manageable to deploy Cilium via Helm directly … and not by injecting a Helm YAML manifest into the K3s manifests dir.
c
thanks, I'll do it in the same way
c
This is what the 
bootstrap
flag on the HelmChart manifest is for. If you set that to true, it will run it on a server node, and with tolerations for not-ready status.
https://rancher.com/docs/k3s/latest/en/helm/#helmchart-field-definitions
spec.bootstrap False Set to True if this chart is needed to bootstrap the cluster (Cloud Controller Manager, etc)
l
Cool @creamy-pencil-82913 - thank you
Will that parameter also help if one injects a Helm chart into the /manifests folder on the first control-plane node? So that after the component is installed will 
bootstrap: True
help one avoid the chart being tried installed again on e.g. node restart? Right now we’re injecting the chart >> then deleting it after installation. Thank you
c
No, it doesn't change anything other than how the install job pod is configured (host net + tolerations)
🎯 1
l
Thank you for elaborating @creamy-pencil-82913
c
thanks a lot @creamy-pencil-82913!
79 Views
Open in Slack
PreviousNext
Powered by