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.

Sign up for GitHub

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

Jump to bottom

Implement wildcard ingress for *adorsys.de and *.adorsys.com #60

Open
nce opened this issue Dec 20, 2022 · 2 comments
Open

Implement wildcard ingress for *adorsys.de and *.adorsys.com #60

nce opened this issue Dec 20, 2022 · 2 comments

Comments

@nce
Copy link
Contributor

nce commented Dec 20, 2022

Guess we'll move the certs to the ssm and use the clustersecret to propagate them to specific namespaces
@nce
Copy link
Contributor Author

nce commented Dec 21, 2022

i'd say we deploy a new clusterIssuer and externaldns with management capabilities for the openshift aws account.

then we set explicitly ingress objects in our new setup.

@nce
Copy link
Contributor Author

nce commented Dec 21, 2022

with the changes implemented in #67 this should be easily possible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nce