Visitar URL original
Clarifies in the docs how works the SA usage on the bundles · Issue #5326 · operator-framework/operator-sdk · GitHub
Skip to content

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

Open

Description

@camilamacedo86

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: #5244 (comment)

Additional context

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

Activity

  1. adambkaplan commented on Oct 27, 2021

    @adambkaplan

    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

  2. added this to the v1.15.0 milestone on Nov 1, 2021
  3. modified the milestones: v1.15.0, v1.16.0 on Nov 8, 2021
  4. added a commit that references this issue on Nov 11, 2021
  5. added a commit that references this issue on Nov 16, 2021
  6. added a commit that references this issue on Nov 30, 2021
  7. 33 remaining items

  8. openshift-bot commented on Oct 28, 2022

    @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

  9. added
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Oct 28, 2022
  10. added
    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
    and removed
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    on Oct 28, 2022
  11. removed their assignment
    on Dec 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

kind/documentationCategorizes issue or PR as related to documentation.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions