apache / apache/apisix-helm-chart

[Help request] Traditional deployment failed if ssl is enabled

Open
#789 2 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Go Template
Stars
289
Forks
282
Avg merge
15h 55m
Merged PRs (30d)
3

Description

Hi team

I am trying to enable HTTPS in APISIX Gateway that I deployed in traditional mode using Helm chart version 2.10.0.
Here is the fragment of values.yaml used to deploy

apisix:
ssl:
enabled: true
existingCASecret: "secret-crt"
certCAFilename: "ca.crt"
fallbackSNI: "localhost"

The secret exists.

My pod doesn't start because of this error
`nginx: [emerg] cannot load certificate "/usr/local/apisix/conf/cert/ssl_PLACE_HOLDER.crt"`

I re-read the documentation and don't see any obvious (for me) error.

What did I miss?

Thanks for your help

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Helm chart's values.yaml SSL configuration for traditional mode, using the reported version 2.10.0 and the shown secret settings. Reproduce the deployment and inspect how the configured secret relates to the missing certificate path; done means the pod starts with HTTPS enabled and uses the existing secret.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.