Generate status subresource for SecretProviderClassPodStatus

[aramase]

The kubebuilder annotations here:

secrets-store-csi-driver/apis/v1/secretproviderclasspodstatus_types.go

Lines 43 to 49 in 57b18e8

	// +kubebuilder:object:root=true
	// +kubebuilder:storageversion
	// +genclient
	// +k8s:deepcopy-gen:interfaces=k8s.io/apimachinery/pkg/runtime.Object
	// SecretProviderClassPodStatus is the Schema for the secretproviderclassespodstatus API
	type SecretProviderClassPodStatus struct {

is missing the kubebuilder:subresource:status bit, example:
https://github.com/vmware-tanzu/pinniped/blob/0f613d1823d8eaa8a6cf3cb4a1d75d664be79a1e/apis/supervisor/config/v1alpha1/types_federationdomain.go.tmpl#L116

This means that the API server isn't creating the status sub resource for the CR, nor is it enforcing the rules between spec/status.

The fix would involve updating the annotations, RBAC, CRDs and then also doing an upgrade and downgrade check for the CR with "legacy" data. Probably also would need a release note that tells people not to try to mix and match old/new images with old/new manifests. In addition, we also need to update any Create calls that set Status and move all Update calls to UpdateStatus.

[aramase]

/assign @mandreap

[k8s-ci-robot]

@aramase: GitHub didn't allow me to assign the following users: mandreap.

Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @mandreap

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mandreap]

/assign

[mandreap]

@aramase should we update the SecretProviderClass as well?

[aramase]

@aramase should we update the SecretProviderClass as well?

yes, let's update it!

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[aramase]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[aramase]

/remove-lifecycle rotten
/lifecycle frozen