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

Sub-chart for openfaas ingress #824

Open
alexellis opened this issue Aug 9, 2021 · 2 comments
Open

Sub-chart for openfaas ingress #824

alexellis opened this issue Aug 9, 2021 · 2 comments

Comments

@alexellis
Copy link
Member

alexellis commented Aug 9, 2021

Description

Create a sub-chart for openfaas ingress records including the OIDC record.

It will make it easier for ArgoCD/Flux users of OpenFaaS to set up ingress records and/or the OIDC plugin.

Context

There is an arkade app for openfaas which templates ingress records and a cert-manager issuer in the openfaas namespace.

https://github.com/alexellis/arkade/blob/master/cmd/apps/openfaas_ingress_app.go
https://github.com/alexellis/arkade/blob/master/cmd/apps/openfaas_ingress_app_test.go

It would be easier to maintain, if a sub-helm chart was created for the ingress records instead, then the arkade app could install the chart instead of maintaining its own templates.

For the hobbyist case where basic auth is being used, or a non-customer, the domain will look like:

  • gateway.example.com

When using the OIDC plugin, the chart should be able to generate the two domains required for using the cookies required i.e.:

  • gateway.openfaas.example.com
  • auth.openfaas.example.com

The key is the common sub-domain, so that the cookie set by the OIDC plugin can be shared with the gateway through the common domain *.openfaas.example.com

The openfaas chart currently has some support for an ingress record, but not both. It could be removed as part of this change. There is also the ability to set a custom TLS cert name for when users are not using cert-manager's annotations support.

https://github.com/openfaas/faas-netes/blob/master/chart/openfaas/values.yaml#L177
https://github.com/openfaas/faas-netes/blob/master/chart/openfaas/templates/ingress.yaml

@ah-f3
Copy link

ah-f3 commented Aug 10, 2021

Whats the benafit of a sub-chart over a optional oidc record?

@alexellis
Copy link
Member Author

Hi @ah-f3 it's explained above, reducing duplication between the two, and separating out the ingress into its own chart for maintainability. There are so many ways to configure Ingress, including Istio. Helm templates can get extremely complicated and most of the guides we use for setting up openfaas use port-forwarding because it works everywhere without any additional setup.

Thanks again for your interest. Do you feel like this affects you in some way as an openfaas user?

Alex

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants