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

Start FAQ docs #66

Merged
merged 1 commit into from
Jan 2, 2017
Merged

Start FAQ docs #66

merged 1 commit into from
Jan 2, 2017

Conversation

bprashanth
Copy link
Contributor

No description provided.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Dec 16, 2016
@k8s-reviewable
Copy link

This change is Reviewable

@bprashanth bprashanth self-assigned this Dec 16, 2016
@bprashanth bprashanth changed the title Start FAQ docs [wip] Start FAQ docs Dec 16, 2016
@coveralls
Copy link

Coverage Status

Coverage increased (+0.04%) to 39.868% when pulling d1a5980 on bprashanth:more_docs into e58524f on kubernetes:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.04%) to 39.868% when pulling f606a85 on bprashanth:more_docs into e58524f on kubernetes:master.

@bprashanth bprashanth force-pushed the more_docs branch 7 times, most recently from de54f9b to f661655 Compare December 21, 2016 21:46
@bprashanth bprashanth changed the title [wip] Start FAQ docs Start FAQ docs Dec 21, 2016
@coveralls
Copy link

Coverage Status

Coverage remained the same at 39.868% when pulling 85c4317 on bprashanth:more_docs into f0762ba on kubernetes:master.

@bprashanth bprashanth assigned aledbf, freehan and MrHohn and unassigned bprashanth Dec 21, 2016
@bprashanth
Copy link
Contributor Author

ready for review

@coveralls
Copy link

Coverage Status

Coverage remained the same at 39.868% when pulling 85c4317 on bprashanth:more_docs into f0762ba on kubernetes:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.04%) to 39.823% when pulling 85c4317 on bprashanth:more_docs into f0762ba on kubernetes:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 39.868% when pulling 85c4317 on bprashanth:more_docs into f0762ba on kubernetes:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 39.868% when pulling 85c4317 on bprashanth:more_docs into f0762ba on kubernetes:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 39.868% when pulling 85c4317 on bprashanth:more_docs into f0762ba on kubernetes:master.


Yes, please see [this](/examples/static-ip) example.

## Does updating a Kubernetes secrete update the GCE TLS certs?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo, secret or secrets


## Does updating a Kubernetes secrete update the GCE TLS certs?

Yes, expect O(30s) delay.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for a faq, prefer something like "up to a minute delay"

Yes, expect O(30s) delay.

The controller should create a second ssl certificate suffixed with `-1` and
atomically swap it with the ssl certificate in your taret proxy, then delete
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo, target proxy


The controller should create a second ssl certificate suffixed with `-1` and
atomically swap it with the ssl certificate in your taret proxy, then delete
the obselete ssl certificate.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo, obsolete

## Is there a maximum number of Endpoints I can add to the Ingress?

This limit is directly related to the maximum number of endpoints allowed in a
Kubernetes cluster, not the the HTTP LB configuration, since the HTTP LB sends
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo, "the the" -> "the"


1. Navigate to the [cloud console](https://console.cloud.google.com/) and click on the "Networking" tab, then choose "LoadBalancing"
2. Find the loadbalancer you'd like to delete, it should have a name formatted as: k8s-um-ns-name--UUID
3. Delete it, check the boxes to also casade the deletion down to associated resources (eg: backend-services)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: "casade" -> "cascade"

If you find yourself in such a situation, you can delete the resources by hand:

1. Navigate to the [cloud console](https://console.cloud.google.com/) and click on the "Networking" tab, then choose "LoadBalancing"
2. Find the loadbalancer you'd like to delete, it should have a name formatted as: k8s-um-ns-name--UUID
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be nice for it to be clear what's a variable and what's not. No clue if "-um-" is literal of meant to stand for something.

e.g. k8s-???-$namespace-$name--$UUID is fairly well understood for indicating variables.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.02%) to 39.89% when pulling 85c4317 on bprashanth:more_docs into f0762ba on kubernetes:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 39.868% when pulling 85c4317 on bprashanth:more_docs into f0762ba on kubernetes:master.

@aledbf
Copy link
Member

aledbf commented Dec 22, 2016

@bprashanth please add a reference to how is possible to achieve IP preservation in gce/gke
(in aws is easy, just enable proxy protocol)

@bprashanth
Copy link
Contributor Author

Yeah, on GCE with today's http lb you can't preserve it (you only get XFF). You can manually setup an ssl proxy (does tls termination and proxy protocol) and point it at the nginx controller (with proxy protocol enabled). I will write an example about this.

@aledbf
Copy link
Member

aledbf commented Dec 22, 2016

@bprashanth
Copy link
Contributor Author

Yeah exactly, they'd need to deploy the nginx ingress contorller, create the ingress with ingress.class and setup the ssl proxy by hand (the gce controller doesn't setup the ssl proxy, it sets up the http lb: https://cloud.google.com/compute/docs/load-balancing/, unfortunately they're 2 different things, the ssl proxy can't do urlmaps etc)

@Draiken
Copy link

Draiken commented Dec 23, 2016

@bprashanth the ssl proxy needs a backend service, which only accepts node pools as backends and also requires a health check.
I'm sorry for my ignorance here but I can't seem to get this working at all.
This seems to work for hosts, not for containers.

Could you point me to an example of this working on GCE/GKE?

The Kubernetes Service is an abstraction over endpoints (pod-ip:port pairings).
The Ingress is an abstraction over Services. This doesn't mean all Ingress
controller must route *through* a Service, but rather, that routing, security
and auth configuration is represented in the Ingerss resource per Service, and
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: s/Ingerss/Ingress/

@bprashanth bprashanth mentioned this pull request Jan 2, 2017
@bprashanth
Copy link
Contributor Author

I'll address comments in a follow up (#102), merging now since I'm on vacation and this doc will answer FAQ while I'm AFK

@bprashanth bprashanth merged commit e76e7d0 into kubernetes:master Jan 2, 2017
haoqing0110 referenced this pull request in stolostron/management-ingress Mar 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants