Use uber calico image for OSS component deployments#4586
Draft
caseydavenport wants to merge 2 commits intotigera:masterfrom
Draft
Use uber calico image for OSS component deployments#4586caseydavenport wants to merge 2 commits intotigera:masterfrom
caseydavenport wants to merge 2 commits intotigera:masterfrom
Conversation
Switch the operator to deploy OSS Calico components (typha, kube-controllers, apiserver, CSI driver) using the consolidated calico/calico uber image instead of per-component images. Each component container now specifies a Command to select the appropriate subcommand (e.g., "calico typha", "calico apiserver"). For kube-controllers, the health check probes are updated to use "calico check-status" instead of the standalone check-status binary. Enterprise (TigeraSecureEnterprise) deployments are unchanged and continue to use per-component images.
Update node.go to use ComponentCalico for the CNI init container and flexvol init container in OSS mode, with appropriate command overrides. Update csi.go to use ComponentCalico for the node-driver-registrar in OSS mode. Also add missing component entries to ignoredImages in gen-versions so that calico_versions.yml entries for goldmane, whisker, webhooks, and other components that the operator doesn't render don't cause build failures.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Switch the operator to deploy OSS Calico components (typha, kube-controllers, apiserver, CSI driver) using the consolidated
calico/calicouber image instead of per-component images. Each component container now specifies aCommandto select the appropriate subcommand (e.g.,calico typha,calico apiserver).For kube-controllers, the health check probes are updated to use
calico check-statusinstead of the standalonecheck-statusbinary.Enterprise (TigeraSecureEnterprise) deployments are unchanged and continue to use per-component images.
Depends on projectcalico/calico#12225 which adds the uber binary and image.