-
Notifications
You must be signed in to change notification settings - Fork 214
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
apisix-ingress-controller Helm Chart features & fixes #704
Comments
Thanks for the PRs @mstefany . I have run the CI and will review your PRs |
@mstefany Can you also update the Readme in your PRs to fix lint tests? like these ones https://github.com/apache/apisix-helm-chart/actions/runs/7490527809/job/20534429629?pr=697#step:4:54 |
@Revolyssup It's updated now, I somehow missed it on this PR. |
@Revolyssup Done. |
@Revolyssup One more PR to fix Prometheus metrics collection, see: #706 |
@Revolyssup One more PR, but this will probably require broader discussion, see: #712 |
@Revolyssup Additional PR: #724, seems that loki-logger is not enabled by default while other logging plugins are (and we need loki). |
Additional PR for review related to Server Tokens: #727 |
We are currently working on implementation of
apisix
into our EKS cluster. And it seems that Helm Chart is missing some of the features or has some bugs. Instead of opening many issues for you to resolve, I have tried to submit PRs with fixes/improvements.We are currently installing
apisix-ingress-controller
Helm Chart using Flux CD, so many things can be workaround usingkustomize
postRenderer
, but having these directly in Helm Chart would make things easier, see:For this matter, I am submitting a overview of PRs for you to review and potentially merge (I don't mind further improving PRs if needed and if review is provided):
There is one more thing missing - support for enabling/disabling apisix plugins in the configMap (e.g. zipkin is enabled by default, but opentelemetry is not, and we would like to have it vice-versa).
EDIT:
Additional PRs:
The text was updated successfully, but these errors were encountered: