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

Value apisix.vault.enabled does nothing #795

Open
JoonaHa opened this issue Jan 21, 2025 · 0 comments
Open

Value apisix.vault.enabled does nothing #795

JoonaHa opened this issue Jan 21, 2025 · 0 comments

Comments

@JoonaHa
Copy link

JoonaHa commented Jan 21, 2025

Hello!
I'm trying to initialize Apisix with Vault integration enabled at start-up.
I have installed the Helm chart by running:

helm install apisix apisix/apisix --create-namespace  --namespace apisix --set apisix.vault.enabled=true --set apisix.vault.host=http://vault-active.vault.svc.cluster.local:8200 --set apisix.vault.prefix=apisix --set apisix.vault.token=root

But when I try to query the configured secrets. There is nothing there.

$ curl --request GET \
  --url http://127.0.0.1:9180/apisix/admin/secrets \
  --header 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1'
{"list":[],"total":0}

If I kubectl exec to the pod I can see the Vault configuration correctly in conf/config.yaml

Have I misunderstood something? Is the Vault configuration read when deployed in traditional mode?
The documentation does not mention any restrictions for apisix.vault.enabled
I have also made sure that there is not any old persistenvolumes for etcd so the aren't any lingering old database files .

Thank you in advance.

JoonaHa added a commit to EURODEO/femdi-gateway-iac that referenced this issue Jan 22, 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

1 participant