apache / apache/apisix-helm-chart
Changing credentials for admin api Error
- Dominant language
- Go Template
- Stars
- 289
- Forks
- 282
- Avg merge
- 15h 55m
- Merged PRs (30d)
- 3
Description
When following the example on the [website](https://apisix.apache.org/docs/ingress-controller/getting-started/get-apisix-ingress-controller/) the apisix deployment won't reach the ready state (1/1) when changing the default credentials.
I use the following command to initialize apisix with the ingresscontroller in standalopne api driven mode
`helm install apisix \`
` --namespace ingress-apisix \`
` --create-namespace \`
` --set apisix.deployment.role=traditional \`
` --set apisix.deployment.role_traditional.config_provider=yaml \`
` --set etcd.enabled=false \`
` --set ingress-controller.enabled=true \`
` --set ingress-controller.config.provider.type=apisix-standalone \`
` --set ingress-controller.apisix.adminService.namespace=ingress-apisix \`
` --set ingress-controller.gatewayProxy.createDefault=true \`
` --set apisix.admin.credentials.admin=abc123 \`
` apisix/apisix`
This is the state in which the cluster is stuck
These are the last logs of the deployment.apps/apisix
What am I missing?
Thanks for your help
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the Helm installation command from the issue and compare it with the linked getting-started example. Inspect the apisix deployment logs and readiness state after changing the admin credential; done means the deployment reaches ready state while using the non-default credential.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100