generated from cloudoperators/repository-template
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Comments
gciezkowski-acc
added a commit
that referenced
this issue
Jan 16, 2025
gciezkowski-acc
added a commit
that referenced
this issue
Jan 17, 2025
gciezkowski-acc
added a commit
that referenced
this issue
Jan 17, 2025
gciezkowski-acc
added a commit
that referenced
this issue
Jan 20, 2025
gciezkowski-acc
added a commit
that referenced
this issue
Jan 20, 2025
gciezkowski-acc
added a commit
that referenced
this issue
Jan 20, 2025
gciezkowski-acc
added a commit
that referenced
this issue
Jan 20, 2025
gciezkowski-acc
added a commit
that referenced
this issue
Jan 20, 2025
gciezkowski-acc
added a commit
that referenced
this issue
Jan 20, 2025
24 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Priority
(Medium) I'm annoyed but I'll live
User Story
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
Reference Issues
No response
The text was updated successfully, but these errors were encountered: