-
Notifications
You must be signed in to change notification settings - Fork 126
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
[Lifecycle] Do not fail deployments #1934
Comments
This is great and will help potential users understand that Keptn is "safe by default". To that end, I would advocate for the default being |
@thisthat would take up this issue |
Hey @YashPimple thanks 👍 |
I'm confused. This is assigned to @YashPimple but Yash says @thisthat will take it up. Concerned that this important safe default is falling through the cracks. I'm happy to work on this if it needs people - just point me in the right direction of the code please and assign to me. This is on the critical path for adoption. |
Hey @agardnerIT, @YashPimple will work on this and by the end of the week he will provide a PR :) |
any updates on this @YashPimple ? |
I've just been hit by something like this again. In this case, I'm using ArgoCD to roll out my cluster in steps (sync waves). Keptn rolls out in wave 5. Backstage (and other components) rolls out after that in wave 6. Keptn could not start (specifically the certificate operator) due to cluster sizing (insufficient CPU). But now that Keptn components cannot start, the admission webhook endpoints are not available. Everything that comes after this is completely blocked. PLEASE PLEASE can we make Keptn safe by default! |
Since there was not coding activity on this issue since Dec 11th, setting the ticket again as free for assignment. Please feel free to re-apply for assignment if you want to work on the ticket! |
Goal
Help user prepare their pre-checks without blocking any deployment
Details
Users that want to adapt Keptn for pre-checks might want to test that they nail down the right set of tasks and evaluations before they can safely run them in production. To support them, we can add a new config option that allows Keptn to run them without blocking the deployment.
Acceptance Criteria
block-deployment
inKeptnConfig
true
block-deployment
istrue
, then the status of WorkloadInstance for pre-tasks and -evaluations is based on the respective action resultsblock-deployment
isfalse
, then the status of WorkloadInstance for pre-tasks and -evaluations is always set to succeed at the end of their executionDoD
The text was updated successfully, but these errors were encountered: