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

Jump to bottom

Classic Calico-Installation (kubectl apply) should have a smaller footprint #9517

Open
erkules opened this issue Nov 22, 2024 · 1 comment · May be fixed by #9518
Open

Classic Calico-Installation (kubectl apply) should have a smaller footprint #9517

erkules opened this issue Nov 22, 2024 · 1 comment · May be fixed by #9518
Labels
kind/enhancement

Comments

@erkules
Copy link

erkules commented Nov 22, 2024

In CAPI there is a way to deploy K8s-objects using ConfigMaps (via ClusterRessourceSets).
The K8s-obejects to deploy Calico are above that 1MB limit for storing Objects in etcd.

$ du -sh tigera-operator.yaml 
1,6M    tigera-operator.yaml

Cilium uses not so much:

$ du -sh cilium.yaml 
64K     cilium.yaml

It would be nice to have a smaller footprint to deploy calico via ClusterRessourceSets in CAPI.
@caseydavenport caseydavenport linked a pull request Nov 22, 2024 that will close this issue
Open
3 tasks
@caseydavenport
Copy link
Member

This PR removes all of the CRD content from tigera-operator.yaml: #9518

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove CRDs from tigera-operator.yaml caseydavenport/calico
3 participants
@erkules @caseydavenport @lwr20