Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Syncing ClusterIP Service from kube uses service port instead of pod port #132

Closed
lkysow opened this issue Sep 16, 2019 · 0 comments · Fixed by #133
Closed

Syncing ClusterIP Service from kube uses service port instead of pod port #132

lkysow opened this issue Sep 16, 2019 · 0 comments · Fixed by #133
Labels
type/bug Something isn't working

Comments

@lkysow
Copy link
Member

lkysow commented Sep 16, 2019

When syncing from Kube to Consul, we use the port of the service instead of the underlying Pods.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Register Endpoint ports for ClusterIP services hashicorp/consul-k8s
1 participant
@lkysow