Anubhav Jindal created IMPALA-15018:
---------------------------------------
Summary: This Epic tracks the upstream effort to provide a
generic, production-oriented Kubernetes deployment path for Apache Impala,
including Helm chart packaging, operator support, configuration management, and
documentation.
Key: IMPALA-15018
URL: https://issues.apache.org/jira/browse/IMPALA-15018
Project: IMPALA
Issue Type: Epic
Reporter: Anubhav Jindal
Assignee: Anubhav Jindal
*Summary*
This Epic tracks the upstream effort to provide a generic, production-oriented
Kubernetes deployment path for Apache Impala, including Helm chart packaging,
operator support, configuration management, and documentation.
*Motivation*
Impala currently lacks a single upstream-owned Kubernetes deployment workflow
that is easy to install, evolve, and review. This Epic organizes incremental
Jira tasks to deliver a clean, ASF-appropriate implementation that supports
common deployment topologies and day-2 operations.
*Scope*
This Epic includes 12 child JIRAs covering:
* Core Impala Helm chart scaffold and component manifests
* HMS integration templating
* Optional Kudu integration resources
* Optional Ranger integration resources
* Runnable values/examples for Kubernetes deployment
* {{ImpalaCluster}} CRD and operator RBAC setup
* Operator deployment bundle and sample CR
* Operator reconciliation logic and chart packaging integration
* Consolidated generic deployment documentation
({{{}impala-on-kubernetes.md{}}})
* Typed operator configuration keys for daemon/query settings
* OAuth auth support for chart/operator config (follow-up Jira)
* Secure-cluster configuration support (follow-up Jira)
*Out of Scope*
* Environment/vendor-specific deployment customizations
* Non-upstream CI/CD or platform tooling integrations
*Success Criteria / Exit Criteria*
* All child JIRAs are resolved and linked to this Epic
* Kubernetes deployment docs and examples are complete and reproducible
* Gerrit review feedback is addressed for each patch series
* Resulting deployment path is generic, upstream-safe, and free of
platform-specific assumptions
*Compatibility / Risk*
Changes are additive and configuration-driven. Default behavior remains
compatible with existing non-Kubernetes workflows; Kubernetes-specific behavior
is isolated to chart/operator paths.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
