wehub-resource-sync
bf2343b7e4
Integration Tests - MySQL + Elasticsearch / Detect Changes (push) Waiting to run
Integration Tests - MySQL + Elasticsearch / integration-tests-mysql-elasticsearch (push) Blocked by required conditions
Integration Tests - PostgreSQL + Elasticsearch + Redis / Detect Changes (push) Waiting to run
Integration Tests - PostgreSQL + Elasticsearch + Redis / integration-tests-postgres-elasticsearch-redis (push) Blocked by required conditions
Integration Tests - PostgreSQL + OpenSearch / Detect Changes (push) Waiting to run
Integration Tests - PostgreSQL + OpenSearch / integration-tests-postgres-opensearch (push) Blocked by required conditions
Java Checkstyle / java-checkstyle (push) Waiting to run
Maven Collate Tests / maven-collate-ci (push) Waiting to run
OpenMetadata Service Unit Tests / Detect Changes (push) Waiting to run
OpenMetadata Service Unit Tests / openmetadata-service-unit-tests (push) Blocked by required conditions
OpenMetadata Service Unit Tests / k8s_operator-unit-tests (push) Blocked by required conditions
OpenMetadata Service Unit Tests / openmetadata-service-unit-tests-status (push) Blocked by required conditions
Publish Package to Maven Central Repository / publish-maven-packages (push) Waiting to run
2.8 KiB
2.8 KiB
Kubernetes Integration Tests
Overview
OpenMetadata has two types of Kubernetes integration tests:
- K8sIngestionPipelineResourceIT - Tests ingestion pipelines using native Kubernetes Jobs/CronJobs
- K8sOMJobOperatorIT - Tests the custom OMJob operator (requires operator deployment)
Key Configuration
TestSuiteBootstrap automatically configures the K8s pipeline client with:
useOMJobOperator=false- Uses native Kubernetes Jobs and CronJobs instead of custom OMJob CRDs
This means all K8s tests use standard Kubernetes resources by default, no custom operators needed!
Running K8s Tests
K8sIngestionPipelineResourceIT (Native Jobs/CronJobs)
This test uses standard Kubernetes resources (Jobs and CronJobs):
# Run with K8s enabled
ENABLE_K8S_TESTS=true mvn test -pl :openmetadata-integration-tests -Dtest=K8sIngestionPipelineResourceIT
# Or using system property
mvn test -pl :openmetadata-integration-tests -DENABLE_K8S_TESTS=true -Dtest=K8sIngestionPipelineResourceIT
The test will:
- Start K3s using TestContainers
- Use native Kubernetes Jobs and CronJobs (not custom CRDs)
- Test pipeline deployment, triggering, deletion, etc.
K8sOMJobOperatorIT (Custom OMJob Operator)
This test is for the custom OMJob operator and is disabled by default:
- Has
@Disabledannotation - Requires the OMJob operator to be deployed in the cluster
- Tests custom CRD functionality
What Happens When K8s is Enabled
- TestSuiteBootstrap starts a K3s container using TestContainers
- Creates namespace
openmetadata-pipelines - Configures the pipeline service client with K3s kubeconfig
- Sets
useOMJobOperator=falseby default (native Jobs/CronJobs) - OpenMetadata server can now deploy pipelines to K8s
Requirements
- Docker must be running
- TestContainers will automatically pull the K3s image
- Tests take ~30-60 seconds longer due to K3s startup
Test Output
When K8s is enabled, you'll see:
K8s tests enabled: true
Starting K3s container with image: rancher/k3s:v1.28.5-k3s1
K3s container started
K8s pipeline service client configured and ready
Troubleshooting
Tests skip with "K8s tests disabled"
- Set
ENABLE_K8S_TESTS=trueenvironment variable - The K8s-only integration tests check the explicit
ENABLE_K8S_TESTSflag before running - When enabled, each K8s test class calls
TestSuiteBootstrap.setupK8s()to initialize its backend
NullPointerException for pipelineServiceClient
- This means the OpenMetadata app started before the K8s pipeline client was applied to the live ingestion resource
TestSuiteBootstrap.setupK8s()now refreshes the registeredIngestionPipelineResourcewhen K8s is enabled on-demand
Tests timeout
- K3s container startup can take 30-60 seconds
- Ensure Docker has sufficient resources allocated