-
Notifications
You must be signed in to change notification settings - Fork 27
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
Renaming the webhook deployment from webhook-server
to webhook
.
#957
Renaming the webhook deployment from webhook-server
to webhook
.
#957
Conversation
@ybettan: GitHub didn't allow me to request PR reviews from the following users: TomerNewman. Note that only kubernetes-sigs members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ybettan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for kubernetes-sigs-kmm ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #957 +/- ##
==========================================
- Coverage 79.09% 72.68% -6.42%
==========================================
Files 51 65 +14
Lines 5109 5762 +653
==========================================
+ Hits 4041 4188 +147
- Misses 882 1395 +513
+ Partials 186 179 -7 ☔ View full report in Codecov by Sentry. |
e6be591
to
f7102a6
Compare
46ce349
to
5e47ec3
Compare
* When we generate files with `controller-gen` it generates a service called `webhook-service` and it is not configurable. * When we deploy KMM with OLM, OLM deploys a service for the webhook called `<webhook-deployment-name>-service. Therefore, before this change, we were getting 2 services for the same deployment. One generated by `controller-gen` and added to the bundle manifests and the other one created "on the fly" by OLM. This change will make OLM find an already existing service called `webhook-service` in the cluster because the deployment is called `webhook`, therefore, it won't create a second service as before. Services in KMM's namespace before the changes: ``` kmm-operator-controller-metrics-service ClusterIP 10.129.169.25 <none> 8443/TCP 2d2h kmm-operator-webhook-server-service ClusterIP 10.130.107.158 <none> 443/TCP 2d2h kmm-operator-webhook-service ClusterIP 10.128.244.171 <none> 443/TCP 2d2h ``` Services in KMM's namespace after the changes: ``` kmm-operator-controller-metrics-service ClusterIP 10.99.75.82 <none> 8443/TCP 88m kmm-operator-webhook-service ClusterIP 10.105.163.241 <none> 443/TCP 88m ``` Signed-off-by: Yoni Bettan <[email protected]>
5e47ec3
to
b6f8178
Compare
/lgtm |
When we generate files with
controller-gen
it generates a service calledwebhook-service
and it is not configurable.When we deploy KMM with OLM, OLM deploys a service for the webhook called
<webhook-deployment-name>-service
.Therefore, before this change, we were getting 2 services for the same deployment. One generated by
controller-gen
and added to the bundle manifests and the other one created "on the fly" by OLM.This change will make OLM find an already existing service called
webhook-service
in the cluster because the deployment is calledwebhook
, therefore, it won't create a second service as before.Services in KMM's namespace before the changes:
Services in KMM's namespace after the changes:
/assign @yevgeny-shnaidman
/cc @TomerNewman