-
Notifications
You must be signed in to change notification settings - Fork 607
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
Consistent and unique container names #2810
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: aliok The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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
/cc @vaikas
@@ -33,7 +33,7 @@ spec: | |||
serviceAccountName: eventing-controller | |||
|
|||
containers: | |||
- name: eventing-controller | |||
- name: channel-broker-controller |
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.
it should just be controller
@@ -33,7 +33,7 @@ spec: | |||
serviceAccountName: eventing-controller | |||
|
|||
containers: | |||
- name: eventing-controller | |||
- name: mt-broker-controller |
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.
controller
I don't like it. I also do not like eventing's usage of non-standard container names but I want them all to be the same for the same purpose, not all unique. /hold |
Eventing operator (and also serving operator) has a feature to override the images for containers that are created by the operator. It works like this:
In this example, image for the container created with name If all container names are not unique, this feature is not usable. Otherwise, I don't care about the container names :D
Maybe we can come up with a proper naming strategy so that they're unique but still very similar as they have the same purpose? |
I think the correct way to implement this in the operator is to use something like an obj ref with a path to know which controller this image override will be targeting. The current plan seems very fragile. It is not the container name you are trying to find, it should be the deployment name + the container name + a namespace. |
Fair enough. I think we found another way on our side to override images and I won't pursue this. /close |
@aliok: Closed this PR. 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/test-infra repository. |
Fixes #2794
Proposed Changes