Skip to content

[v1 API Review] Update Installed Status condition usage #1291

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Tracked by #740
everettraven opened this issue Sep 20, 2024 · 1 comment · Fixed by #1314
Closed
Tracked by #740

[v1 API Review] Update Installed Status condition usage #1291

everettraven opened this issue Sep 20, 2024 · 1 comment · Fixed by #1314
Assignees
Labels
epic/v1-api v1.0 Issues related to the initial stable release of OLMv1

Comments

@everettraven
Copy link
Contributor

everettraven commented Sep 20, 2024

The Installed status condition represents whether or not a bundle is installed. It should be set to True once the initial installation is successful. If it was set to True, it should transition to False, or be removed, ONLY IF all workloads associated with the ClusterExtension have been removed from the cluster. When unset, this condition should be interpreted the same as "False". Successful upgrades should update this condition and other status fields with the appropriate values to reflect the state of the currently installed bundle.

Acceptance Criteria:

  • The logic for setting the Installed status condition is updated to:
    • Set the Installed status condition to True and status.install.bundle field with installed bundle information after initial installation is successful
    • Update the Installed status condition and status.install.bundle field to reflect the currently installed bundle information after a successful upgrade
    • Set the Installed status condition to False if there are any failures encountered during the initial installation attempt
    • Only transition from True to False if all workloads associated with the ClusterExtension have been removed from the cluster (having not looked into it further, this may mean we never perform this transition)

For more information, see the RFC

@everettraven everettraven added v1.0 Issues related to the initial stable release of OLMv1 epic/v1-api labels Sep 20, 2024
@trgeiger
Copy link
Contributor

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic/v1-api v1.0 Issues related to the initial stable release of OLMv1
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants