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.

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

Can't deploy Mix protocols loadbalancer in Azure Kubernetes 1.13.5 #81406

singhania opened this issue Aug 14, 2019 · 2 comments


Copy link

commented Aug 14, 2019

I am using below yaml to deploy a loadbalancer service which as per the document should deploy a loadbalancer with mixed protocol but same was not working.
apiVersion: v1
kind: Service
annotations: 'true' "true"
name: abc-xyz
namespace: abc
app: abc-xyz
externalTrafficPolicy: Local
type: LoadBalancer
- name: xyz-pickle
port: 2004
protocol: TCP
- name: xyz-plain
port: 2003
protocol: TCP
- name: xyz-gui
port: 8080
protocol: TCP
- name: xyz-admin
port: 8126
protocol: TCP
-name: xyz
port: 8125
protocol: UDP
app: abc-xyz

@singhania singhania added the kind/bug label Aug 14, 2019


This comment has been minimized.

Copy link

commented Aug 14, 2019

@singhania: There are no sig labels on this issue. Please add a sig label by either:

  1. mentioning a sig: @kubernetes/sig-<group-name>-<group-suffix>
    e.g., @kubernetes/sig-contributor-experience-<group-suffix> to notify the contributor experience sig, OR

  2. specifying the label manually: /sig <group-name>
    e.g., /sig scalability to apply the sig/scalability label

Note: Method 1 will trigger an email to the group. See the group list.
The <group-suffix> in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals.

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.


This comment has been minimized.

Copy link

commented Aug 15, 2019

/sig azure

These SIGs are my best guesses for this issue. Please comment /remove-sig <name> if I am incorrect about one.

🤖 I am a bot run by vllry. 👩‍🔬

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.