calico: upstream pr preparation#7
Conversation
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
The user can install calico (even using the same flannel port) via a CRD for it, adding the rules for it, customizing the Daemonset env and the addresses that the containers use. Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
9efd023 to
602ebb4
Compare
|
@AkihiroSuda please take a look at these changes. |
There was a problem hiding this comment.
Why does this need to be a daemonset?
Could be in https://github.com/rootless-containers/usernetes/tree/master/Dockerfile.d
There was a problem hiding this comment.
We also had it as a COPY to the container via a udev rules files, but I don't think it took. At least whatever state changes the initial calico install triggered might have undone it.
| wget https://raw.githubusercontent.com/projectcalico/calico/refs/heads/release-v3.31/manifests/calico.yaml -O $CALICO_FILE | ||
|
|
||
| # backend to vxlan | ||
| yq eval-all -i '(select(.kind == "ConfigMap" and .metadata.name == "calico-config").data.calico_backend) = "vxlan"' $CALICO_FILE |
There was a problem hiding this comment.
Can we use helm with values.yaml ?
https://docs.tigera.io/calico/latest/getting-started/kubernetes/helm
There was a problem hiding this comment.
No we tried for weeks to get helm working - it was too complex. If you want to try and are successful we can do some testing of what you find.
Signed-off-by: Vanessa Sochat <814322+vsoch@users.noreply.github.com>
Signed-off-by: Vanessa Sochat <814322+vsoch@users.noreply.github.com>
Signed-off-by: Vanessa Sochat <814322+vsoch@users.noreply.github.com>
This is for our environment and I do not think is wanted here. Signed-off-by: Vanessa Sochat <814322+vsoch@users.noreply.github.com>
I'm not sure if this will be possible, but I'm trying to cleanup our current calico install. I was able to install from a release and then apply our custom manifests, but (so far) haven't been able to do the entire thing cleanly with yq. It's a weird case of needing to apply the initial setup they have, but then remove it and re-apply the customizations, importantly keeping the IP: autodetect set so the calico.vxlan network shows up with
ip addr. I am finding that when I try to patch from the getgo with yq I run into a myriad of errors. If I don't create our customizations with autodetect the network has issues too. I still think it might be possible, and the next step is to look closely at what we have for the individual configs here and compare with what is being installed upstream.Update: I've now removed all custom manifests - we get the upstream manifest and make all changes with yq. There are quite a few, but I think this is probably the slimmiest I can get it for something to review / easily see changes.