Skip to content
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

Closed
4 tasks
thisthat opened this issue Aug 23, 2023 · 8 comments · Fixed by #3123
Closed
4 tasks

[Lifecycle] Do not fail deployments #1934

thisthat opened this issue Aug 23, 2023 · 8 comments · Fixed by #3123

Comments

@thisthat
Copy link
Member

thisthat commented Aug 23, 2023

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

  • Add a new entry block-deployment in KeptnConfig
  • Default value should be true
  • If block-deployment is true, then the status of WorkloadInstance for pre-tasks and -evaluations is based on the respective action results
  • If block-deployment is false, then the status of WorkloadInstance for pre-tasks and -evaluations is always set to succeed at the end of their execution

DoD

  • Documentation is updated
  • A user can execute pre-checks without blocking deployments if the configuration is enabled
@thisthat thisthat added status: ready-for-refinement Issue is relevant for the next backlog refinment lifecycle-operator labels Aug 23, 2023
@thisthat thisthat added this to the 0.10 milestone Aug 23, 2023
@agardnerIT
Copy link
Contributor

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 false.

@thisthat thisthat moved this to 🎟️ Refined in Keptn Lifecycle Toolkit Sep 6, 2023
@thisthat thisthat removed the status: ready-for-refinement Issue is relevant for the next backlog refinment label Sep 6, 2023
@YashPimple
Copy link
Member

@thisthat would take up this issue

@thisthat
Copy link
Member Author

thisthat commented Sep 7, 2023

Hey @YashPimple thanks 👍

@agardnerIT
Copy link
Contributor

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.

@StackScribe StackScribe added status: ready-for-refinement Issue is relevant for the next backlog refinment status: needs-discussion labels Oct 11, 2023
@thisthat
Copy link
Member Author

Hey @agardnerIT, @YashPimple will work on this and by the end of the week he will provide a PR :)

@thisthat thisthat removed status: ready-for-refinement Issue is relevant for the next backlog refinment status: needs-discussion labels Oct 11, 2023
@mowies
Copy link
Member

mowies commented Nov 27, 2023

any updates on this @YashPimple ?

@agardnerIT
Copy link
Contributor

agardnerIT commented Jan 18, 2024

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!

@odubajDT
Copy link
Contributor

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!

@odubajDT odubajDT added the good first issue Good for newcomers label Feb 13, 2024
@mowies mowies removed this from the 0.12 milestone Feb 20, 2024
@odubajDT odubajDT self-assigned this Feb 21, 2024
@odubajDT odubajDT removed the good first issue Good for newcomers label Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment