-
-
Notifications
You must be signed in to change notification settings - Fork 1
feat: Add Service on top of operators #534
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but I'd perhaps wait on merging until we have implemented a webhook for an operator and/or wait until the release branches are cut (around 10th July).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Rollout to operators Products
|
Part of stackabletech/issues#642
Needed for stackabletech/operator-rs#1066
This PR only adds a Service on top of the operator Pod. This is needed, so that k8s can call the conversion webhook.
IMHO we can add this right now and start using it later.
This unblocks merging stackabletech/operator-rs#1066, as that PR needs to
OPERATOR_NAMESPACE
andOPERATOR_SERVICE_NAME
env vars