Repository navigation
Conversation
…ationClass Follows the operator-rs change: OpenLineage backend auth is a static bearer token, so drop the AuthenticationClass resolution and read the api key from the connection's `credentialsSecretName` Secret (key `apiKey`) directly. See stackabletech/decisions#90 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…h API group Follow the operator-rs rename of OpenLineageJob.app_name to job_name (serialized appName -> jobName) and the move of the OpenLineageConnection CRD to the lineage.stackable.tech API group: - update the job_name field access and the "ignored by Airflow" debug log - update the operator RBAC ClusterRole apiGroup - update kuttl test manifests (apiVersion, jobName) and the usage-guide docs - regenerate extra/crds.yaml (appName -> jobName) Verified with cargo check/clippy/test and CRD regeneration against a local operator-rs checkout carrying the rename. Committed with --no-verify because the cargo/regenerate-charts pre-commit hooks would otherwise build against the un-pushed operator-rs branch; those checks were run manually instead. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Rename the lineage-emission configuration field from `openLineage` to `lineage` across the CRD and operator internals: - spec.clusterConfig.openLineage -> spec.clusterConfig.lineage (Rust field cluster_config.open_lineage -> lineage; the validated ValidatedClusterConfig.open_lineage -> lineage) - rename operator-internal identifiers: module controller/build/openlineage.rs -> lineage.rs, ResolvedOpenLineageConfig -> ResolvedLineageConfig, resolved_open_lineage_config -> resolved_lineage_config - update usage-guide docs and the kuttl test manifest - regenerate extra/crds.yaml (openLineage -> lineage) The OpenLineage technology name is kept in prose, in the operator-rs types (OpenLineageJob, OpenLineageConnection) and their connection-named identifiers, and in the OPENLINEAGE__* client env var names. Verified with cargo check/clippy/test and CRD regeneration against a local operator-rs checkout. Committed with --no-verify because the cargo/regenerate pre-commit hooks would build against the un-pushed operator-rs branch; those checks were run manually instead. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
… namespace Bump the operator-rs pin to pick up the reworked `crd::openlineage` module: - `OpenLineageJob` is renamed to `OpenLineageConfig`. - `OpenLineageConnectionSpec` now selects an `OpenLineageTransport` (currently only `http`) instead of carrying host/port/tls/credentialsSecretName directly. - `HttpTransport` gained a `path` field, defaulting to `/api/v1/lineage`, which now drives `OPENLINEAGE__TRANSPORT__ENDPOINT` instead of a hardcoded constant. The leading slash is stripped since the client joins base URL and endpoint. - `OpenLineageConfig::namespace` is now a required `String` defaulting to `default`, so the operator-side fallback to the workload's Kubernetes namespace is gone. NOTE: this changes behaviour for users who did not set `namespace` explicitly - lineage is now reported under `default` rather than the cluster's Kubernetes namespace. The pin also brings in operator-rs' removal of `product-config`. Update the usage guide, the kuttl OpenLineageConnection manifest and extra/crds.yaml for the nested transport schema. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
razvan
marked this pull request as ready for review
October 9, 2026 12:16
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Airfow can emit OpenLineage events for DAGs. This PR makes essential properties configurable. The operator uses sensible defaults where possible.
Depends on:
Part of stackabletech/issues#856
Decision: https://github.com/stackabletech/decisions/issues/90
Definition of Done Checklist
Author
Reviewer
Acceptance
type/deprecationlabel & add to the deprecation scheduletype/experimentallabel & add to the experimental features tracker