[
https://issues.apache.org/jira/browse/IMPALA-15317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anubhav Jindal updated IMPALA-15317:
------------------------------------
Epic Color: ghx-label-7 (was: ghx-label-3)
> Add a design document for the Impala Kubernetes Operator
> --------------------------------------------------------
>
> Key: IMPALA-15317
> URL: https://issues.apache.org/jira/browse/IMPALA-15317
> Project: IMPALA
> Issue Type: Task
> Reporter: Anubhav Jindal
> Assignee: Anubhav Jindal
> Priority: Major
>
> *Problem Statement*
> The operator has grown across multiple changes (CRD behavior, RBAC hardening,
> Helm integration, secure-cluster options, and E2E testing). Today, design
> intent is spread across PR discussions and code comments, which makes
> onboarding and future changes harder.
>
> *Proposed Change*
> Add a design doc to the Impala repo that describes:
> - goals and non-goals of the operator
> - high-level architecture and control flow (CR -> reconcile -> Helm release
> lifecycle)
> - namespace model and ownership expectations
> - RBAC model and least-privilege boundaries
> - configuration surface (CRD fields + chart values mapping)
> - optional component handling (e.g., LDAP, Kudu, Ranger)
> - failure handling, idempotency, and observability expectations
> - test strategy (unit + chart validation + k8s E2E)
>
> *Scope*
> This JIRA is documentation-only and does not change runtime behavior.
>
> *Acceptance Criteria*
> - Design document is added to the repository.
> - Document is linked from the relevant operator/helm docs index/readme.
> - Key operator decisions and trade-offs are captured clearly enough for new
> contributors to implement follow-up work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
