You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor(openlineage): use credentialsSecretName instead of AuthenticationClass
Follows the operator-rs change: read the OpenLineage backend bearer token from
the connection's `credentialsSecretName` Secret (key `apiKey`) instead of
resolving a Static AuthenticationClass.
See stackabletech/decisions#90
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
<1> References an `AuthenticationClass` by name (cluster-scoped). If omitted, no authentication is used.
111
-
<2> Only the `static` provider is supported for OpenLineage. Other providers (LDAP, OIDC, TLS) are rejected with an error.
112
-
<3> Name of the Secret holding the token. Must exist in the same namespace as the `TrinoCluster`.
113
-
<4> The Secret must be in the cluster's namespace so it can be projected into the coordinator.
114
-
<5> The token must be stored under the fixed key `apiKey`. The token is mounted as a file into the coordinator and resolved into the event listener configuration at startup, so it never appears in the ConfigMap or the pod's environment.
100
+
<1> Name of the Secret holding the token. If omitted, no authentication is used. The Secret must exist in the same namespace as the `TrinoCluster`.
101
+
<2> The Secret must be in the cluster's namespace so it can be projected into the coordinator.
102
+
<3> The token must be stored under the fixed key `apiKey`. The token is mounted as a file into the coordinator and resolved into the event listener configuration at startup, so it never appears in the ConfigMap or the pod's environment.
115
103
116
104
The operator translates this into the OpenLineage HTTP transport's `api-key` (bearer) authentication.
117
105
Combine it with the `tls` block above when the backend also needs TLS server verification.
0 commit comments