[go] v1.18.0 Migration - Missing `generate bundle` requirement for "control-plane" label

[adambkaplan]

trafficstars

When migrating from operator-sdk v1.17.0 to v1.18.0, generate bundle now looks for a deployment with the control-plane: controller-manager label pair. The main container must also be named manager.

Previously, developers were free to rename the main container or drop the "control-plane" label (or it was never generated in the first place).

This was not documented in the migration guide [1].

[1] https://sdk.operatorframework.io/docs/upgrading-sdk-version/v1.18.0/

[varshaprasad96]

@adambkaplan This was a known change brought from Kubebuilder. Sorry, for missing this in the documentation. Unfortunately, SDK is now on 1.33 release, and 1.18 seems too old, we currently do not support more than n-3 releases. It would be difficult to make this change in the documentation, but if there are any particular concerns we can address them through issues.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci[bot]]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.