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

[EOEPCA/IAM] Provisioning of the APISIX Ingress controller (PEP) as template for other BBs #12

Open
w-jfe opened this issue Jul 1, 2024 · 0 comments
Open

[EOEPCA/IAM] Provisioning of the APISIX Ingress controller (PEP) as template for other BBs #12

w-jfe opened this issue Jul 1, 2024 · 0 comments
Assignees
@w-scho
Milestone
Q3 - Release Beta...

Comments

@w-jfe
Copy link
Collaborator

w-jfe commented Jul 1, 2024 •
edited by w-scho
Loading

Currently the IAM BB's APISIX ingress controller is preconfigured primarily for direct use within the IAM BB.
A template shall be provided that simplifies the configuration of APISIX for use with other BBs. This should cover BBs that are deployed in the same cluster as the IAM as well as BBs that are deployed in a separate cluster and want to make use of APISIX as an ingress controller / PEP in conjunction with the IAM BB.
@w-jfe w-jfe added this to the Q2 - Release Beta #01 milestone Jul 1, 2024
@w-jfe w-jfe changed the title Provisioning of the APISIX Ingress controller (PEP) as template for other BBs [EOEPCA/IAM] Provisioning of the APISIX Ingress controller (PEP) as template for other BBs Jul 1, 2024
@w-scho w-scho self-assigned this Oct 28, 2024
@w-scho w-scho mentioned this issue Nov 29, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@w-scho w-scho

Labels
None yet
Projects
None yet
Milestone
Q3 - Release Beta #02
Development

No branches or pull requests
2 participants
@w-jfe @w-scho