Skip to content
This repository has been archived by the owner on Mar 10, 2023. It is now read-only.

[Feature Request] Custom domains on OFC using IngressOperator #646

Open
Waterdrips opened this issue Jun 3, 2020 · 1 comment
Open

[Feature Request] Custom domains on OFC using IngressOperator #646

Waterdrips opened this issue Jun 3, 2020 · 1 comment

Comments

@Waterdrips
Copy link
Contributor

There has been requests to allow custom domains in OFC (#520)

We now have FunctionIngress CRD provided by the IngressOperator provided as an option in the ofc-bootstrap installer.

We could read annotations like

com.openfaas.cloud.custom-domain: "my-fn.example.com"
com.openfaas.cloud.custom-domain.tls: true

and create the FunctionIngress CRD.

Provided a user points their domain at the cluster (A or CNAME? ) then they could get a LetsEncrypt TLS cert if they wanted.

Im suggesting:

  • Default TLS to false (LE rate limit, people might not want to lock their accounts out)
  • Only 1 custom domain per function
@Waterdrips
Copy link
Contributor Author

cc @alexellis issue for discussions

@alexellis alexellis changed the title [ Feature ] Custom domains on OFC uisng the provided IngressOperator [Feature Request] Custom domains on OFC using \IngressOperator Oct 5, 2020
@alexellis alexellis changed the title [Feature Request] Custom domains on OFC using \IngressOperator [Feature Request] Custom domains on OFC using IngressOperator Oct 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant