Skip to content

✨ bump helm-operator-plugins to v0.3.0; disable failure rollbacks - #1020

Merged
grokspawn merged 1 commit into
operator-framework:mainfrom
joelanford:disable-automatic-rollback
Jul 9, 2024
Merged

✨ bump helm-operator-plugins to v0.3.0; disable failure rollbacks#1020
grokspawn merged 1 commit into
operator-framework:mainfrom
joelanford:disable-automatic-rollback

Conversation

@joelanford

@joelanfordjoelanford commented Jul 8, 2024

Copy link
Copy Markdown
Member

Description

This PR bumps to a new version of helm-operator-plugins, which brings a few new fixes, features, and changes. Notably:

  • ActionClientGetter: allow disabling rollbacks after failures

This PR also:

  • makes use of the new ActionClientGetter knob so that operator-controller no longer rolls back a failed install or upgrade.
  • sets a max version history of 10 to avoid unlimited piling up of release secrets
  • uses helm's new server-side dry-run option, which provides cluster information to helm templates (e.g. when using the lookup template function).

For all changes, see https://github.com/operator-framework/helm-operator-plugins/releases/tag/v0.3.0

Closes#994

Reviewer Checklist

  • API Go Documentation
  • Tests: Unit Tests (and E2E Tests, if appropriate)
  • Comprehensive Commit Messages
  • Links to related GitHub Issue(s)

@openshift-ciopenshift-ciBot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 8, 2024
@openshift-merge-robotopenshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 8, 2024
@netlify

netlifyBot commented Jul 8, 2024

Copy link
Copy Markdown

Deploy Preview for olmv1 ready!

NameLink
🔨 Latest commitcaf4d3d
🔍 Latest deploy loghttps://app.netlify.com/sites/olmv1/deploys/668caed3536d500008ca58ba
😎 Deploy Previewhttps://deploy-preview-1020--olmv1.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@joelanford
joelanfordforce-pushed the disable-automatic-rollback branch from c69ef81 to 06d987eCompareJuly 8, 2024 20:40
@openshift-merge-robotopenshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 8, 2024
@codecov

codecovBot commented Jul 8, 2024

Copy link
Copy Markdown

Codecov Report

Attention: Patch coverage is 85.71429% with 1 line in your changes missing coverage. Please review.

Project coverage is 78.07%. Comparing base (235e3d4) to head (caf4d3d).
Report is 1 commits behind head on main.

FilesPatch %Lines
...nternal/controllers/clusterextension_controller.go75.00%1 Missing ⚠️
Additional details and impacted files
@@ Coverage Diff @@## main #1020 +/- ##
==========================================
+ Coverage 78.05% 78.07% +0.02% 
==========================================
Files 18 18 Lines 1253 1259 +6 ==========================================
+ Hits 978 983 +5 - Misses 193 194 +1 
Partials 82 82 
FlagCoverage Δ
e2e56.78% <85.71%> (+0.13%)⬆️
unit53.21% <0.00%> (-0.26%)⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@joelanford

joelanford commented Jul 9, 2024

Copy link
Copy Markdown
MemberAuthor

With the failure rollbacks disabled, I am seeing the expected exponential backoffs retrying (and still failing; in my case I changed a manifest to be invalid, so i expect permafailure). And then when I patch the clusterextension to allow choosing a working version, I see that upgrade go through and the installation succeed.

- disable failure rollbacks
- set max helm release history to 10
Signed-off-by: Joe Lanford <joe.lanford@gmail.com>
@joelanford
joelanfordforce-pushed the disable-automatic-rollback branch from 06d987e to caf4d3dCompareJuly 9, 2024 03:30
@joelanford
joelanford marked this pull request as ready for review July 9, 2024 03:32
@joelanford
joelanford requested a review from a team as a code ownerJuly 9, 2024 03:32
@openshift-ciopenshift-ciBot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 9, 2024
@joelanfordjoelanford changed the title ⚠ bump helm-operator-plugins to v0.3.0; disable failure rollbacks✨ bump helm-operator-plugins to v0.3.0; disable failure rollbacksJul 9, 2024
@grokspawn
grokspawn added this pull request to the merge queue Jul 9, 2024
Merged via the queue into operator-framework:main with commit 8947c3dJul 9, 2024
@joelanford
joelanford deleted the disable-automatic-rollback branch July 20, 2024 01:59
perdasilva pushed a commit to LalatenduMohanty/operator-controller that referenced this pull request Aug 13, 2024
- disable failure rollbacks
- set max helm release history to 10
Signed-off-by: Joe Lanford <joe.lanford@gmail.com>
@skattojuskattoju mentioned this pull request Sep 25, 2024
4 tasks
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

operator-controller should not uninstall/rollback a failed install/upgrade

3 participants

@joelanford@grokspawn@openshift-merge-robot