[
https://issues.apache.org/jira/browse/IMPALA-15043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18104499#comment-18104499
]
ASF subversion and git services commented on IMPALA-15043:
----------------------------------------------------------
Commit 6e7c6b0e46d99ead5b85a03abc14772a6afadc5d in impala's branch
refs/heads/master from Anubhav Jindal
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=6e7c6b0e4 ]
IMPALA-15043: Add Kubernetes-in-Docker E2E scripts
Add Kubernetes-in-Docker support for external-cluster smoke tests by adding
Jenkins orchestration, runtime selection (kind or k3d), and a service-to-pod
port-forward fallback path for HS2 connectivity checks.
Move the K8s E2E trigger from bin/jenkins/all-tests.sh into
bin/run-all-tests.sh as an opt-in stage (K8S_E2E_TEST=false by default).
Update script ergonomics: use /usr/bin/env bash shebangs, preserve an
existing IMPALA_HOME, run from the repo root, use impala-python3 in the HS2
readiness probe, and reuse cleanup() for failed port-forward setup.
Set ENABLE_BEESWAX=false in the K8s external-cluster runner instead of
changing ImpalaTestSuite client setup semantics.
Relocate the architecture guide out of docs/ into
helm/impala/kubernetes-in-docker-e2e.md and update README references.
Testing:
- bash -n bin/jenkins/all-tests.sh
- bash -n bin/run-all-tests.sh
- bash -n bin/jenkins/run-k8s-e2e-tests.sh
- bash -n bin/run-k8s-e2e-tests.sh
- ./bin/run-k8s-e2e-tests.sh --dry-run -k TestK8sExternalCluster --maxfail=1
- ./bin/jenkins/run-k8s-e2e-tests.sh --dry-run
- python3 bin/jenkins/critique-gerrit-review.py --dryrun
Change-Id: I122b99c38c8c70ab535349f92212621330f2aa55
Assisted-by: GPT-5.3 (Cursor)
Reviewed-on: http://gerrit.cloudera.org:8080/24372
Reviewed-by: Jason Fehr <[email protected]>
Tested-by: Jason Fehr <[email protected]>
> Enable end-to-end test execution against Kubernetes deployments
> ---------------------------------------------------------------
>
> Key: IMPALA-15043
> URL: https://issues.apache.org/jira/browse/IMPALA-15043
> Project: IMPALA
> Issue Type: Task
> Reporter: Anubhav Jindal
> Assignee: Anubhav Jindal
> Priority: Major
>
> h3. Background
> Impala now has upstream Kubernetes deployment support (Helm/operator), but
> upstream automated runtime validation is still centered on the local
> minicluster model.
> h3. Problem
> Current {{custom_cluster}} tests are not a good fit for Kubernetes validation
> because they restart local daemons between tests via minicluster tooling.
> This creates a gap: we lack an upstream-supported way to run meaningful E2E
> coverage against a real, externally deployed K8s Impala cluster.
> h3. Proposal
> Add an external-cluster/Kubernetes test mode that can run existing end-to-end
> style tests against a pre-provisioned K8s cluster without invoking
> minicluster start/stop flows. Reuse existing test harness pieces where
> possible, while clearly separating this mode from restart-dependent
> {{custom_cluster}} behavior.
> h3. Initial Scope
> * Add configuration/entrypoint support for connecting test clients to
> external Impala/Kudu/HMS endpoints.
> * Define and enable a stable initial E2E subset compatible with persistent
> external clusters.
> * Document setup, required inputs, and execution steps for manual and CI
> runs.
> h3. Out of Scope (Initial)
> * Full migration of restart-dependent {{custom_cluster}} coverage.
> * Replacing existing minicluster-based CI jobs.
> * Covering all optional auth/security permutations in the first iteration.
> h3. Success Criteria
> * Reproducible command path for running E2E tests against Kubernetes.
> * At least one stable upstream test suite running in this mode.
> * Existing minicluster workflows remain unchanged.
> h3. Testing
> * Manual validation against a Kubernetes test cluster.
> * CI validation for the new external-cluster mode.
> * Regression checks confirming no breakage to current minicluster test
> execution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
