-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Add DeploymentConflictingPorts analyzer #30049
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
Add DeploymentConflictingPorts analyzer #30049
Conversation
/test integ-telemetry-mc-k8s-tests_istio |
…service-conflicting-ports
- name: "DeploymentConflictingPorts" | ||
code: IST0137 | ||
level: Warning | ||
description: "If we have two services, both selecting the same workload, with the same target port, they should be the same port." |
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.
Reword without "if"? Perhaps "Two services selecting the same workload with same target port are MUST refer to the same port."
code: IST0137 | ||
level: Warning | ||
description: "If we have two services, both selecting the same workload, with the same target port, they should be the same port." | ||
template: "This deployment %s is associated with multiple services %v using targetPort %s but different ports: %v." |
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.
Nit: use %q instead of %s if port name can be empty.
@esnible Thanks, updated. |
@esnible Do i need to do something else? |
/retest |
#29302
[X] User Experience
[X] Developer Infrastructure
[X] Does not have any changes that may affect Istio users.