[
https://issues.apache.org/jira/browse/IMPALA-15016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anubhav Jindal updated IMPALA-15016:
------------------------------------
Epic Link: IMPALA-15018
> Add OAuth authentication options to Impala Helm chart
> -----------------------------------------------------
>
> Key: IMPALA-15016
> URL: https://issues.apache.org/jira/browse/IMPALA-15016
> Project: IMPALA
> Issue Type: Task
> Reporter: Anubhav Jindal
> Assignee: Anubhav Jindal
> Priority: Major
>
> *Problem*
> The current Impala Helm chart supports LDAP and Ranger-related options, but
> does not expose OAuth authentication configuration for {{{}impalad{}}}.
> Review feedback on {{IMPALA-14974}} requested OAuth support since it is
> commonly used in Kubernetes environments.
> *Proposed Change*
> Add Helm values and template wiring to configure OAuth-related {{impalad}}
> startup flags in a typed and discoverable way.
> The change should:
> * Introduce OAuth config keys under {{values.yaml}} (for example, enablement
> and provider settings)
> * Render corresponding {{impalad}} args only when OAuth is enabled
> * Keep existing LDAP behavior unchanged and backward-compatible
> * Document usage in chart examples and Kubernetes deployment docs
> *Testing*
> * Run {{helm lint}} for the chart
> * Run {{helm template}} and verify OAuth args are rendered only when enabled
> * Deploy on a test Kubernetes cluster and validate {{impalad}} starts with
> expected OAuth flags
> * Verify no behavior change when OAuth config is omitted
> *Compatibility/Risk*
> Low risk. Defaults remain unchanged, and OAuth flags are opt-in.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
