Closed acheuk closed 2 years ago
@scottchc1 do you think for those edge cases we need to expose it as separate variable or use additional values? Or not document it at all? I think we should introduce HTTPD_USE_SSL_CERT_CHAIN standalone in this case
i don't know enough about what use case this change serves. maybe @Gazza7205 can review? i would treat additionalEnv meant to be optional, and should be empty in most standard deployment. so if this env must exist and have a default value (doesn't matter true or false, as long as the env key need to exist), then declare it explicitly.
I think this should be an optional variable. @melil02, can you confirm?
Agree, lets not expose it for now.
@acheuk - should we close this PR or do you want to keep it open?
Closing this PR per comment above.
…spatcher.
Description of the change
Add environment variable to show certificate chain for dispatcher.
Benefits
Drawbacks
Applicable issues
Additional information
Checklist
Chart.yaml
according to semver.[charts/gateway]
)values-production.yaml
apart fromvalues.yaml
, ensure that you implement the changes in both files