[
https://issues.apache.org/jira/browse/IMPALA-15017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anubhav Jindal updated IMPALA-15017:
------------------------------------
Epic Link: IMPALA-15018
> Add secure-cluster configuration support to Impala Helm chart
> -------------------------------------------------------------
>
> Key: IMPALA-15017
> URL: https://issues.apache.org/jira/browse/IMPALA-15017
> Project: IMPALA
> Issue Type: Task
> Reporter: Anubhav Jindal
> Assignee: Anubhav Jindal
> Priority: Major
>
> *Problem*
> The current Helm-based deployment focuses on non-secure defaults and does not
> provide a complete, documented path for secure-cluster configuration (for
> example TLS/Kerberos-related settings). Review feedback on {{IMPALA-14974}}
> requested secure-cluster support.
> *Proposed Change*
> Extend chart values and templates to support secure deployment configuration
> for Impala components.
> The change should:
> * Add structured security-related values in {{values.yaml}}
> * Wire required daemon flags/env/volume mounts/secrets references in
> templates
> * Preserve current defaults for non-secure quickstart deployment
> * Add documentation for secure setup, including required secrets/config
> inputs
> *Testing*
> * Run {{helm lint}} and {{helm template}} for secure and non-secure
> configurations
> * Validate secure settings render correctly and are gated behind explicit
> values
> * Deploy to a test Kubernetes cluster configured for security and validate
> component startup
> * Re-check non-secure deployment path remains functional
> *Compatibility/Risk*
> Medium risk due to security-sensitive configuration surface; mitigated by
> opt-in defaults and explicit documentation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
