[
https://issues.apache.org/jira/browse/IMPALA-15317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18114307#comment-18114307
]
ASF subversion and git services commented on IMPALA-15317:
----------------------------------------------------------
Commit cc7152527ee4d77cc8d1aa7a6d9de3816ebf932d in impala's branch
refs/heads/master from Anubhav Jindal
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=cc7152527 ]
IMPALA-15317: Add operator design document
Add a design document for the Impala Kubernetes Operator that captures
its architecture, reconcile model, configuration mapping, namespace
model, RBAC/security boundaries, packaging, and testing strategy in one
canonical place.
The operator has grown across several changes in the Impala on
Kubernetes epic, and its design intent was previously spread across
review discussions and code. This document consolidates that context so
new contributors can understand the operator and extend it safely.
The document is documentation-only and does not change runtime behavior.
It carries an ASF license header so it passes RAT without a new exclude
entry, matching the existing helm/impala markdown docs. The helm README
links to it from the operator section.
Testing:
- Verified ASF license header matches existing RAT-compliant markdown
- Verified relative link from helm/impala/README.md resolves
- python3 bin/jenkins/critique-gerrit-review.py --dryrun
Change-Id: Ie18d6cb9217fa68599866745acc5b7ea6fce2574
Assisted-by: Claude (Cursor)
Reviewed-on: http://gerrit.cloudera.org:8080/24763
Reviewed-by: Jason Fehr <[email protected]>
Tested-by: Jason Fehr <[email protected]>
> 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]
