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
Allow connectors and individual tasks to opt into short-lived service-principal tokens while keeping PAT as the unchanged default authentication mode.
Signed-off-by: Rohit Sharma <rohitrsh@gmail.com>
To configure Spark in the Flyte deployment's backend, follow [Step 1](https://docs.flyte.org/en/latest/deployment/plugins/k8s/index.html#deployment-plugin-setup-k8s), [2](https://docs.flyte.org/en/latest/flytesnacks/examples/k8s_spark_plugin/index.html).
12
12
13
13
All [examples](https://docs.flyte.org/en/latest/flytesnacks/examples/k8s_spark_plugin/index.html) showcasing execution of Spark jobs using the plugin can be found in the documentation.
14
+
15
+
## Databricks authentication
16
+
17
+
The Databricks connector uses PAT authentication by default, preserving the
18
+
existing `databricks-token` namespace Secret and
19
+
`FLYTE_DATABRICKS_ACCESS_TOKEN` fallback.
20
+
21
+
OAuth machine-to-machine (M2M) authentication can be enabled on the connector:
22
+
23
+
```yaml
24
+
env:
25
+
- name: FLYTE_DATABRICKS_AUTH_TYPE
26
+
value: oauth_m2m
27
+
- name: DATABRICKS_CLIENT_ID
28
+
value: "<service-principal-client-id>"
29
+
- name: DATABRICKS_CLIENT_SECRET
30
+
valueFrom:
31
+
secretKeyRef:
32
+
name: databricks-connector-oauth
33
+
key: client_secret
34
+
```
35
+
36
+
For per-namespace identities, create a `databricks-oauth` Secret in each
0 commit comments