vivekhegadems opened a new issue, #11485: URL: https://github.com/apache/apisix/issues/11485
### Description I have deployed apisix in standalone mode by configuring values.yaml as mentioned in https://apisix.apache.org/docs/apisix/deployment-modes/#standalone All things look fine. There is no issue with the deployment As I understand in standalone mode deployment of apisix, all routes/ssl certificates will be configured in yaml that will be included via configmap and it will be mounted as local file to apisix container as the "config_provider: yaml" is set to yaml. I am checking if there is any way to use certificates created from cert-manager in apisix standalone mode deployment. Need inputs on the same. Is there a way to use the certificates created using cert-manager in apisix standalone mode deployment? I tried the way as mentioned in https://apisix.apache.org/docs/ingress-controller/tutorials/manage-certificates-with-cert-manager/, and reference the secret that includes certificates tls section of values.yaml. But this doesn't work. Maybe because of the standalone mode deployment of apisix which uses only reference from yaml. Problem with apisix standalone mode is the certificates will need to be statically configured in the yaml as mentioned in https://apisix.apache.org/docs/apisix/deployment-modes/#how-to-enable-ssl. ### Environment - APISIX version (run `apisix version`): Latest apisix-2.8.1 - Operating system (run `uname -a`): Linux ace2-sn-2 4.18.0-513.9.1.el8_9.x86_64 #1 SMP Thu Nov 16 10:29:04 EST 2023 x86_64 x86_64 x86_64 GNU/Linux - OpenResty / Nginx version (run `openresty -V` or `nginx -V`): - etcd version, if relevant (run `curl http://127.0.0.1:9090/v1/server_info`): - APISIX Dashboard version, if relevant: - Plugin runner version, for issues related to plugin runners: - LuaRocks version, for installation issues (run `luarocks --version`): -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
