-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
🐛 (kustomize/v2): fix ServiceMonitor with TLS kustomize scaffolding #4536
🐛 (kustomize/v2): fix ServiceMonitor with TLS kustomize scaffolding #4536
Conversation
|
Welcome @abhishekdwivedi3060! |
Hi @abhishekdwivedi3060. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
docs/book/src/cronjob-tutorial/testdata/project/config/default/kustomization.yaml
Show resolved
Hide resolved
cb1d070
to
97071c1
Compare
path: /spec/endpoints/0/tlsConfig | ||
value: | ||
# SERVICE_NAME and SERVICE_NAMESPACE will be substituted by kustomize | ||
serverName: SERVICE_NAME.SERVICE_NAMESPACE.svc |
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.
Did we only need to change the kustomize default file just to pass the serviceName right?
But that is fixed. It will always be the same.
Could we not simplify the changes and the default kustomize by adding here the name
serverName: SERVICE_NAME.SERVICE_NAMESPACE.svc | |
serverName: controller-manager-metrics-monitor.SERVICE_NAMESPACE.svc |
Instead?
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.
I am trying to see if we can avoid do changes at: config/default/kustomization.yaml
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.
I tried to follow the existing convention followed in kubebuilder kustomize files.
For other scenarios where the service name is referred, we follow similar convention of replacements. See certificate
I'm not sure if this serverName
replacement is any different. Let me know if my understanding is wrong
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.
I will need a few time to check/think about this one.
But I will be back to you ASAP
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.
I am not too happy with the complexities in the kustomize, but I think that is not part of the scope, and it makes sense you follow the same approach. Thank you.
/ok-to-test |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhishekdwivedi3060, camilamacedo86 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 |
Fixes #4533
config/prometheus/monitor_tls_patch.yaml
fielserverName
field inmonitor_tls_patch.yaml
for metric server cert validation