operator-sdk icon indicating copy to clipboard operation
operator-sdk copied to clipboard

Clarifies in the docs how works the SA usage on the bundles

Open camilamacedo86 opened this issue 4 years ago • 3 comments

What is the URL of the document?

https://sdk.operatorframework.io/docs/olm-integration/

Which section(s) is the issue in?

https://sdk.operatorframework.io/docs/olm-integration/tutorial-bundle/

What needs fixing?

Describe how OLM manages the SA: https://github.com/operator-framework/operator-sdk/issues/5244#issuecomment-950917221

Additional context

Doc the info to avoid others failing in the same scenario.

camilamacedo86 avatar Oct 26 '21 18:10 camilamacedo86

One potential issue is that the migration instructions for v1.5.0 ask developers to specifically create the ServiceAccount manifest [1]. When make bundle is run, it generates the serviceaccount YAML for the bundle, and many projects check this file into version control.

It seems that the bundle's SA manifest be removed when upgrading to v1.13.1?

https://sdk.operatorframework.io/docs/upgrading-sdk-version/v1.5.0/#gov3-add-a-systemcontroller-manager-serviceaccount-to-your-project

adambkaplan avatar Oct 27 '21 18:10 adambkaplan

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 avatar Sep 28 '22 01:09 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 avatar Oct 28 '22 08:10 openshift-bot