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

Adds gateway to expose internal services #174

Merged
merged 1 commit into from
Mar 23, 2024

Conversation

sulochan
Copy link
Collaborator

This patch adds the common gateway (flex-gateway) in nginx-gateway namespace. This gateway will be shared by all other namespaces to expose services internally. To do so the service that is getting exposed internally simply need to follow the fqdn naming of *.sjc.ohthree.com and ref the flex-gateway.

Also, adding the http routes for prometheus and alertmanager that use the above method to expose the two services internally.

This patch adds the common gateway (flex-gateway) in nginx-gateway
namespace. This gateway will be shared by all other namespaces to
expose services internally. To do so the service that is getting
exposed internally simply need to follow the fqdn naming of
*.sjc.ohthree.com and ref the flex-gateway.

Also, adding the http routes for prometheus and alertmanager that
use the above method to expose the two services internally.
@cloudnull
Copy link
Contributor

👍🏼 lgtm - Can you add a doc entry about this?

@sulochan
Copy link
Collaborator Author

👍🏼 lgtm - Can you add a doc entry about this?

https://docs.rackspacecloud.com/infrastructure-gateway-api/

Docs already in.

@cloudnull cloudnull merged commit d0298a4 into rackerlabs:main Mar 23, 2024
2 checks passed
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

Successfully merging this pull request may close these issues.

2 participants