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] Provisioning of the APISIX Ingress controller (PEP) as template for other BBs #12

Closed
w-jfe opened this issue Jul 1, 2024 · 1 comment
Assignees

Comments

@w-jfe
Copy link
Collaborator

w-jfe commented Jul 1, 2024

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
Copy link
Collaborator

w-scho commented Jan 10, 2025

The iam-bb Helm chart allows installing APISIX separately from the other IAM components and can be used to deploy a preconfigured standalone APISIX instance (usable as a PEP) in a separate cluster. Furthermore, templates and documentation for APISIX route and protection configuration have been provided in the scope of #59.

@w-scho w-scho closed this as completed Jan 10, 2025
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