-
Notifications
You must be signed in to change notification settings - Fork 38.9k
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
Fix load-balancer firewall messages #11254
Fix load-balancer firewall messages #11254
Conversation
cluster. If you want to expose this service to the external internet, you may | ||
need to set up firewall rules for the service port(s) (%s) to serve traffic. | ||
|
||
See http://releases.k8s.io/HEAD/docs/services-firewalls.md for more details. |
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: since this is kubectl, it feels like we can confirm and tell them one way or another (not expecting it in this pr).
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.
Ai gree we could, but we pretty much need that to come from the
cloud-provider, which means from the master.
On Tue, Jul 14, 2015 at 1:12 PM, Prashanth B notifications@github.com
wrote:
In pkg/kubectl/cmd/create.go
#11254 (comment)
:out.Write([]byte(msg)) } if obj.Spec.Type == api.ServiceTypeNodePort {
msg := fmt.Sprintf(`
You have exposed your service on an external port on all nodes in your cluster.
If you want to expose this service to the external internet, you may need to set up
- firewall rules for the service port(s) (%s) to serve traffic.
See https://github.com/GoogleCloudPlatform/kubernetes/tree/master/docs/services-firewalls.md for more details.
`, makePortsString(obj.Spec.Ports, true))
msg := fmt.Sprintf(
+cluster. If you want to expose this service to the external internet, you may`You have exposed your service on an external port on all nodes in your
+need to set up firewall rules for the service port(s) (%s) to serve traffic.
+
+See http://releases.k8s.io/HEAD/docs/services-firewalls.md for more details.Nit: since this is kubectl, it feels like we can confirm and tell them one
way or another (not expecting it in this pr).—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/11254/files#r34613478
.
LGTM |
GCE e2e build/test passed for commit 8da6aef5acf9933e93890810aa304c033f30737a. |
8da6aef
to
670141b
Compare
GCE e2e build/test passed for commit 670141b1973dedc64123b4fb2dcf090527420522. |
670141b
to
85a56ce
Compare
GCE e2e build/test passed for commit 85a56ce6d3efa9c42c253c9968125630263e4316. |
85a56ce
to
9005c5b
Compare
GCE e2e build/test passed for commit 9005c5b4d89ba2218b8afc1ef230728f84971304. |
I'd prefer to eliminate the message than to just fix formatting. We don't have warnings about privileged mode, use of PD, or anything else that requires external action by the user. If we're not going to eliminate it, how about we reduce it to 1 line:
docs/services-firewalls.md is out of date, though. It still instructs GCE users to open the firewall with gcloud. |
182b0a9
to
2d4df16
Compare
OK, message removed, docs updated. On Tue, Jul 14, 2015 at 8:35 PM, Brian Grant notifications@github.com
|
LGTM |
cc @davidopp, who is planning to move services-firewalls.md |
GCE e2e build/test failed for commit 182b0a98e57b4f7e5a35afdb76a69f98927568f2. |
GCE e2e build/test passed for commit 2d4df16215e77e27e22142074df2b6961a93d7d9. |
2d4df16
to
fe89298
Compare
GCE e2e build/test passed for commit fe89298. |
all green let's merge now before @davidopp re-creates his PR to move services-firewalls.md. |
Fix load-balancer firewall messages
It seems weird to have services-firewall.md at the top-level of the docs tree, but I couldn't decide where to put it, so I left it there in my PR. It seems like it belongs in user-guide? |
(My PR actually didn't move services-firewall.md, because I couldn't figure out which subdir to put it in.) |
…4-upstream-release-1.0 Automated cherry pick of #11254 upstream release 1.0
I'd say user-guide On Wed, Jul 15, 2015 at 2:23 AM, David Oppenheimer <notifications@github.com
|
No description provided.