-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Docs explaining the new ingress-to-route controller #8596
Conversation
@knobunc PTAL |
This is for openshift/origin#18658 |
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.
We should mention how this works with claiming rules, and how secrets are handled.
Also we should talk about when the objects are deleted.
architecture/networking/routes.adoc
Outdated
== Support for Kubernetes Ingress objects in Openshift | ||
|
||
In an effort to support the Kubernetes method of managing external access to services | ||
in a cluster an ingress to route controller has been created. This controller watches |
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.
Can we use Ingress and Route consistently (or ingress and route)
architecture/networking/routes.adoc
Outdated
@@ -833,3 +833,53 @@ $ oc expose service/<name> --hostname="m.api.openshift.org" | |||
$ oc expose service/<name> --hostname="kates.net" | |||
$ oc expose service/<name> --hostname="api.kates.net" | |||
---- | |||
|
|||
|
|||
== Support for Kubernetes Ingress objects in Openshift |
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.
"OpenShift"
kind: Route | ||
apiVersion: route.openshift.io/v1 | ||
metadata: | ||
name: test-a34th |
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.
Maybe a callout to say that the name is automatically generated, with the ingress's name as a prefix.
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.
Added in the description
cec4689
to
d7b6117
Compare
spec: | ||
rules: | ||
- host: test.com | ||
http: |
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.
there is extra spaces before http:
Verified with @JacobTanenbaum that this was technically ok. I made a new PR for this: @zhaozhanqi this included validating the YAML. Please let me know if there's anything more needed. |
Docs associated with Claytons addition of a route-to-ingress controller
PR18658