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

[FEAT] - Split deployment of Greenhouse controller manager #808

Open
2 tasks
IvoGoman opened this issue Dec 17, 2024 · 0 comments
Open
2 tasks

[FEAT] - Split deployment of Greenhouse controller manager #808

IvoGoman opened this issue Dec 17, 2024 · 0 comments
Labels
feature ready Backlog Item is ready for Sprint Backlog

Comments

@IvoGoman
Copy link
Contributor

Priority

(Medium) I'm annoyed but I'll live

User Story

As an Operator of the Greenhouse platform I want to deploy the operator and the webhooks separately, so that a failing operator deployment does not block Admission and Helm rollback.

Description

The Greenhouse Helm chart has one deployment to rollout the controller manager, which runs both the Operator and the Webhooks.
The goal of the issue is that the Operator and the Webhooks are deployed separately. This ensures that among others that Greenhouse CR's can still be applied when the Operator is failing.
There are already environment variables in place to run the operator in webhook only or controller only mode.

Acceptance Criteria

  • Helm Chart has separate deployments for webhook and operator
  • Metrics are scraped for both deployments

Reference Issues

No response

@github-project-automation github-project-automation bot moved this to Sprint Backlog in Greenhouse Core Roadmap Dec 17, 2024
@IvoGoman IvoGoman added the ready Backlog Item is ready for Sprint Backlog label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature ready Backlog Item is ready for Sprint Backlog
Projects
Status: Sprint Backlog
Development

No branches or pull requests

1 participant