Skip to content

Rename tigera-guardian components to guardian#3845

Merged
Brian-McM merged 1 commit intotigera:masterfrom
Brian-McM:bm-rename-tigera-guardian-to-guardian
Apr 2, 2025
Merged

Rename tigera-guardian components to guardian#3845
Brian-McM merged 1 commit intotigera:masterfrom
Brian-McM:bm-rename-tigera-guardian-to-guardian

Conversation

@Brian-McM
Copy link
Contributor

@Brian-McM Brian-McM commented Mar 28, 2025

Description

Since tigera-guardian has been moved to the calico-system namespace we've decided to remove the tigera prefix since it's redundant

The container name needs to stay the same so the overrides API doesn't break.

For PR author

  • Tests for change.
  • If changing pkg/apis/, run make gen-files
  • If changing versions, run make gen-versions

For PR reviewers

A note for code reviewers - all pull requests must have the following:

  • Milestone set according to targeted release.
  • Appropriate labels:
    • kind/bug if this is a bugfix.
    • kind/enhancement if this is a a new feature.
    • enterprise if this PR applies to Calico Enterprise only.

Release Note

The tigera-guardian deployment and resources previously in the tigera-guardian namespace have been moved to the calico-system namespace. The `tigera-` prefix has been remove for all namespaced resources and replaced with `calico-` for all cluster resources.

Custom policies or RBAC written for these moved components will need to account for the namespace and name changes.

GuardianContainerName = "tigera-guardian"
GuardianServiceName = "guardian"
GuardianVolumeName = "guardian-certs"
GuardianSecretName = "tigera-managed-cluster-connection"
Copy link
Member

Choose a reason for hiding this comment

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

Any reason this can't be guardian-managed-cluster-connection or calico-managed-cluster-connection or just managed-cluster-connection?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We don't create this secret, it's done in CC / the management cluster.

Copy link
Member

Choose a reason for hiding this comment

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

Not asking you to do this now, but seems like it should probably be a SecretRef on the ManagedClusterConnection resource rather than hard-coded.

@caseydavenport
Copy link
Member

@rene-dekker @Brian-McM is there something currently blocking this one?

Since tigera-guardian has been moved to the calico-system namespace we've decided to remove the tigera prefix since it's redundant

The container name needs to stay the same so the overrides API doesn't break.
@Brian-McM Brian-McM force-pushed the bm-rename-tigera-guardian-to-guardian branch from 7f78ab8 to 0c0e419 Compare April 2, 2025 17:45
@Brian-McM Brian-McM merged commit aed7208 into tigera:master Apr 2, 2025
5 checks passed
@Brian-McM Brian-McM deleted the bm-rename-tigera-guardian-to-guardian branch April 2, 2025 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants