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

Support Grout Wildcards #1439

Merged
merged 2 commits into from
Aug 5, 2024
Merged

Support Grout Wildcards #1439

merged 2 commits into from
Aug 5, 2024

Conversation

abhinavsingh
Copy link
Owner

@abhinavsingh abhinavsingh commented Aug 5, 2024

Grout Wildcards

Why

Suppose you have a service which wants to handle requests over ad-hoc subdomains. E.g. Kubernetes cluster services exposed via custom subdomains.

Let's imagine your top level domain is custom.example.com and you want your service to handle HTTP/HTTPS traffic over custom.example.com and *.custom.example.com.

Setup

  1. Configure a HTTPS load balancer for custom.example.com
  2. Send traffic to Grout service IP addresses

PS: Sorry, currently SSL termination must be handled by you.

Connect

grout https://localhost:8080 custom.domain.com --wildcard
2024-08-05 18:24:59,294 - grout - Logged in as someone@gmail.com
2024-08-05 18:25:03,159 - setup - Grouting https://*.custom.domain.com

Now all requests to custom.example.com and *.custom.example.com will reach your grout client.

Viola!!!

@abhinavsingh abhinavsingh added the bot:chronographer:skip PR using this label is exempted from CHANGELOG management label Aug 5, 2024
@abhinavsingh abhinavsingh merged commit 2dbc8af into develop Aug 5, 2024
52 checks passed
@abhinavsingh abhinavsingh deleted the grout-wildcards branch August 5, 2024 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot:chronographer:skip PR using this label is exempted from CHANGELOG management
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant