Skip to content

Add corona calico#5

Open
vsoch wants to merge 3 commits intodevelopfrom
add-corona-calico
Open

Add corona calico#5
vsoch wants to merge 3 commits intodevelopfrom
add-corona-calico

Conversation

@vsoch
Copy link
Copy Markdown
Member

@vsoch vsoch commented Jan 22, 2026

This is a cleaned up variant to install calico to corona.

This needs a full testing, and looks like some manual work for the rebase.

@vsoch vsoch force-pushed the add-corona-calico branch 2 times, most recently from cb78c27 to 0ec0c90 Compare January 22, 2026 05:43
vsoch added 2 commits January 22, 2026 12:50
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 <[email protected]>
@vsoch vsoch force-pushed the add-corona-calico branch from 0ec0c90 to 073e26f Compare January 22, 2026 20:50
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

This file is too lengthy and almost completely unreviewable.
Should this be taken from the upstream?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I thought you might say that!

We made some changes for our setup. I could find a way to get from the upstream. I remember you had a command to do edits in place for yaml - could you show me how to do that?

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Do you mean yq ?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Yes! That sounds right.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

OK - will be testing a patch strategy this morning.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Not able to test - something is going on with the container access on our cluster - I am not able to pull anything for the setup.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

OK - was able to get the containers working, and I've been working on this since. I was able to work through the vxlan setup and separate the CRD install to be from upstream, and then our customizations of the daemonset, configmap, and deployment to be separate:

#7

It's a bit cleaner but still too much to review. I tried to do the entire thing with yq but ran into a lot of issues - I think what is happening is that we need the initial creation to happen and for state to change on the node via the daemonset, and then we have to apply our customized daemonset plus removing the ip autodetect. The logical next step is to compare each of the configmap, daemonset, and deployment carefully and try to figure out if it can be more fully automated with yq.

@AkihiroSuda I will get back to this but I need a break - been working on this all day.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Update: got it down to just the upstream apply, and then changes with yq. There are quite a few, primarily vxlan in the configmap and then environment additions / changes for Felix for the daemonset to support rootless.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants