-
Notifications
You must be signed in to change notification settings - Fork 706
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
2010: fix to expose correct monitoring port #1405
Conversation
pulling latest changes from kubeflow/tf-operator to deepak-muley/tf-operator
training-operator exposes 8080 per logs 2021-09-14T19:31:49.294Z INFO controller-runtime.metrics metrics server is starting to listen {"addr": ":8080"} hence when we do local testing, it works fine but when we expose it using make deploy then inside k8s, its not exposed
@Jeffwan could you please review. |
/hold |
/remove-hold |
I like it! |
/lgtm Thanks for the help! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Jeffwan 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 |
/test kubeflow-tf-operator-presubmit |
fixes kubeflow/manifests#2010 |
ref: kubeflow/manifests#2010
training-operator exposes 8080 per logs
2021-09-14T19:31:49.294Z INFO controller-runtime.metrics metrics server is starting to listen {"addr": ":8080"}
hence when we do local testing, it works fine
but when we expose it using make deploy then inside k8s, its not exposed
Steps: