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

[EOEPCA/IAM] Make APISIX an infrastructure service and use it as the primary ingress controller #76

Open
w-scho opened this issue Jan 14, 2025 · 1 comment

Comments

@w-scho
Copy link
Collaborator

w-scho commented Jan 14, 2025

APISIX is currently deployed as part of the IAM BB and uses a separate ingress on apx.develop.eoepca.org.
It should be deployed as an infrastructure service in a separate namespace ingress-apisix and on the standard ingress develop.eoepca.org.
It is foreseen to deploy a separate new instance of APISIX that replaces the NginX ingress controller as a first step and drop the existing "old" APISIX instance as a second step.
This issue us a follow-up of #63.

@rconway
Copy link
Contributor

rconway commented Jan 27, 2025

See Deployment Guide Ingress Controller Setup - which steers towards APISIX as primary.

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

No branches or pull requests

2 participants