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

[Docs] Update docs on Exposing EL outside cluster #1217

Closed
dibyom opened this issue Sep 1, 2021 · 1 comment · Fixed by #1289
Closed

[Docs] Update docs on Exposing EL outside cluster #1217

dibyom opened this issue Sep 1, 2021 · 1 comment · Fixed by #1289
Assignees
Labels
kind/documentation Categorizes issue or PR as related to documentation.

Comments

@dibyom
Copy link
Member

dibyom commented Sep 1, 2021

The page mentions Exposing an EventListener using a Kubernetes Ingress object would not work on GKE. I think Ingress should work on GKE now.

https://github.com/tektoncd/triggers/blob/63c2ad7f7ad26f8ce9a106d76cf81068996bbf55/docs/eventlisteners.md#exposing-an-eventlistener-outside-of-the-cluster

@dibyom dibyom added the kind/documentation Categorizes issue or PR as related to documentation. label Sep 1, 2021
@dibyom dibyom self-assigned this Sep 27, 2021
@dibyom
Copy link
Member Author

dibyom commented Nov 17, 2021

We should also highlight the serviceType field with LoadBalancer as a easy way to expose the EL in hosted K8s clusters.

@dibyom dibyom added this to the Triggers v0.18 milestone Nov 17, 2021
dibyom added a commit to dibyom/triggers that referenced this issue Dec 21, 2021
The section was quite a bit out of date. I added a section on `LoadBalancer`
services and removed the section on using a Nginx based ingress installed on
the cluster. The Nginx ingress was added as a workaround since early versions
of GKE did not fully support `Ingress` objects. That is now not the case and a
regular Ingress will work fine in GKE.

Fixes tektoncd#1217

Signed-off-by: Dibyo Mukherjee <dibyo@google.com>
tekton-robot pushed a commit that referenced this issue Dec 21, 2021
The section was quite a bit out of date. I added a section on `LoadBalancer`
services and removed the section on using a Nginx based ingress installed on
the cluster. The Nginx ingress was added as a workaround since early versions
of GKE did not fully support `Ingress` objects. That is now not the case and a
regular Ingress will work fine in GKE.

Fixes #1217

Signed-off-by: Dibyo Mukherjee <dibyo@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant