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

Wildcard domains #148

Open
alex-bezek opened this issue Feb 14, 2023 · 0 comments
Open

Wildcard domains #148

alex-bezek opened this issue Feb 14, 2023 · 0 comments
Labels
enhancement New feature or request priority/medium

Comments

@alex-bezek
Copy link
Collaborator

Description

The k8s ingress spec specifies that it does support wildcard hostnames https://kubernetes.io/docs/concepts/services-networking/ingress/#hostname-wildcards
For other ingress controllers which are simply proxy servers, they can set up rules to handle wildcard hosts and leave the dns up to the user. With ngrok, a matcher rule doesn't do anything if an edge isn't setup with an actual host with dns routing to it, so we'll need to setup an edge.

Currently if you try to use a wildcard, you get this error

2023-02-14T16:57:35Z	ERROR	controllers.ingress	Failed to sync ingress to store	{"error": "Domain.ingress.k8s.ngrok.com \"*-bezek-hello-world-ingress-ngrok-io\" is invalid: metadata.name: Invalid value: \"*-bezek-hello-world-ingress-ngrok-io\": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')"}

Use Case

Allow the utilization of wildcard domains

Related issues

No response

@alex-bezek alex-bezek added enhancement New feature or request needs-triage Issues that need triage labels Feb 14, 2023
@alex-bezek alex-bezek removed the needs-triage Issues that need triage label Mar 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority/medium
Projects
None yet
Development

No branches or pull requests

1 participant