Open camilamacedo86 opened 2 years ago
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?
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
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
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.