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.

Sign up for GitHub

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

Jump to bottom

Update Ingress-how-to.md #60

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update Ingress-how-to.md #60

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions Ingress-how-to.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,9 +22,9 @@ spec:
```

You can add any other field needed to your configuration, the important thing here is `endpointPublishingStrategy: Private`.
This will create a set of pods in teh openshift-ingress namespace with prefix: `router-my-keepalived-ingress`.
This will create a set of pods in the openshift-ingress namespace with prefix: `router-my-keepalived-ingress`.

Create a load balancer service to server these pods:
Create a load balancer service to serve these pods:

```yaml
kind: Service
Expand All @@ -49,7 +49,7 @@ spec:
type: LoadBalancer
```

At this point the keepalievd operator will provision a VIP and the routers are reachable there.
At this point the keepalievd operator will provision a VIP and the routers will be reachable there.

If you need to control which IP the router needs to be serve on, use an external IPs:

Expand Down Expand Up @@ -78,6 +78,6 @@ spec:
type: ClusterIP
```

At this point the only missing ingredient is to make sure that the DNS routes requests to `*.myingress.mydomain` are directed to the IP that was provisioned by the keepalived-operator or that was selected via the external IP.
Copy link
Collaborator

Choose a reason for hiding this comment

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

this is correct, please don't change it.

At this point the only missing ingredient are to make sure that the DNS routes requests to `*.myingress.mydomain` are directed to the IP that was provisioned by the keepalived-operator or that was selected via the external IP.

If you are using the [external-dns](https://github.com/kubernetes-sigs/external-dns) operator, you can easily automate this step by adding the following annotation to the service: `external-dns.alpha.kubernetes.io/hostname: *.myingress.mydomain`.