-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Added info for routes to accept ingress objects #8109
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -144,6 +144,40 @@ $ systemctl restart atomic-openshift-master-api atomic-openshift-master-controll | |
|
||
---- | ||
|
||
[[admin-guide-managing-networking-ingress]] | ||
== Setting up the HAProxy router to accept ingress objects | ||
|
||
By default, the HAProxy router only accepts route objects. You can set up the | ||
HAProxy router as a Kubernetes | ||
link:https://kubernetes.io/docs/concepts/services-networking/ingress/[Ingress | ||
Controller] so that it accepts both route and ingress objects. If configured, | ||
the same rules apply for claiming a domain for a namespace based on the creation | ||
time of the object. For example, the oldest route winning against any other | ||
claimants wanting to use the same namespace. | ||
|
||
For example, ownership of routes is based on the claims made for that host name with the same namespace. The oldest route wins against any other claims. | ||
|
||
While this makes the router compatible with Kubernetes ingress | ||
objects, some caveats exist: | ||
|
||
* Ingress objects store the keys and certificates in secrets, so the router needs permission to read all secrets in the system. | ||
* Ingress objects only support edge termination for *https* routes. | ||
|
||
To configure an existing router to have Ingress support (assuming the default | ||
name of `router` for the deployment configuration and the service-account): | ||
|
||
. Set the `ROUTER_ENABLE_INGRESS` environment variable to `true`: | ||
+ | ||
---- | ||
$ oc env dc router ROUTER_ENABLE_INGRESS=true` | ||
---- | ||
|
||
. Add the cluster-admin role to the router: | ||
+ | ||
---- | ||
$ oc adm policy add-role-to-user cluster-admin router` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Below two role should be added to sa router,
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. maybe |
||
---- | ||
|
||
[[admin-guide-controlling-egress-traffic]] | ||
== Controlling Egress Traffic | ||
|
||
|
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.
In order to describe the comparison, I mentioned the router only accepts route objects. Is this accurate?
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.
That is correct.