-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Validation Enhancement: type:LoadBalancer with firewall rules does not open node ports on minions. Service functions from within pods. #34625
Comments
Closing, this appears to be a kops + aws + 1.4 issue. Moved to here. |
After getting help from @justinsb on Slack. This is due to the |
needs repro |
Hmm, might be fixed already? Should repro anyway.
|
Maybe this is an easy one to slash-close :) Prateek will tell us :)
…On Thu, Jun 1, 2017 at 2:43 PM, Dan Williams ***@***.***> wrote:
Hmm, might be fixed already? Should repro anyway.
commit 9e1c886
Author: Maciej Kwiek ***@***.***>
AuthorDate: Thu Sep 22 16:07:47 2016 +0200
Commit: Maciej Kwiek ***@***.***>
CommitDate: Thu Sep 29 10:17:29 2016 +0200
Validate None Service ClusterIP against LB type
If the Service is a Load Balancer, it should not have None Cluster IP.
If it does, Service validation fails.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#34625 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFVgVBMujnoPL71MRuGyeF3eM5rxlxDGks5r_zBvgaJpZM4KU-wn>
.
|
Update on this? |
I think this was fixed. Original issue by Tim : #33036 Fixed by Maciej in PR: #33274 Code at https://github.com/kubernetes/kubernetes/blob/master/pkg/api/validation/validation.go#L2710 : |
Sorry, for the delay. I verified this on GCE and issue is fixed here is the error I get - kubectl apply -f nginx-service.yaml |
Thanks!
…On Mon, Jun 12, 2017 at 12:23 AM, Prateek Gogia ***@***.***> wrote:
Sorry, for the delay. I verified this on GCE and issue is fixed here is
the error I get -
kubectl apply -f nginx-service.yaml
deployment "frontend" created
The Service "frontend" is invalid: spec.clusterIP: Invalid value: "None":
may not be set to 'None' for LoadBalancer services
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#34625 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFVgVNYbEBJtbTgGiBDJFi187-isQXE5ks5sDOdngaJpZM4KU-wn>
.
|
Kubernetes version (use
kubectl version
):Client Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.0", GitCommit:"a16c0a7f71a6f93c7e0f222d961f4675cd97a46b", GitTreeState:"clean", BuildDate:"2016-09-26T18:16:57Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.0", GitCommit:"a16c0a7f71a6f93c7e0f222d961f4675cd97a46b", GitTreeState:"clean", BuildDate:"2016-09-26T18:10:32Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}
Environment:
uname -a
):Linux ip-172-20-0-155 3.16.0-4-amd64 Unit test coverage in Kubelet is lousy. (~30%) #1 SMP Debian 3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/LinuxBelow are the yaml files used to reproduce the issue.
storageclass.yaml
master-pod.yaml
pg-slave-rs-1.yaml
pg-services.yaml
What happened:
ELB is allocated and the node port for the ELB is not allocated on the minion. As a result, the ELB will never have any nodes in service. The service (write) has the following output from describe.
kubectl describe svc postgres-test-write
Output of netstat on the minion
netstat -plnt |grep 30238
is emptyHitting the service postgres-test-write within another pod works correctly.
What you expected to happen:
Ports to be allocated on the node, and the ELB to function properly. The security groups are correct. The correct security group is created for the ELB with the correct rules, and this security group is added as an allow all to the minion security groups.
How to reproduce it (as minimally and precisely as possible):
Use the yaml above to reproduce my setup after spinning up a new 1.4 cluster on AWS with ./kube-up.sh
Anything else do we need to know:
I'll be happy to provide any additional logging.
The text was updated successfully, but these errors were encountered: