#7259 [Flyte 7198] Enabling flyte plugins
Pull request opened by
0yukali0
Tracking issue
Close
#7198
Why are the changes needed?
Flyte v2 OSS won't trigger ray, dask, spark, torch, tensorflow and mpi plugins
What changes were proposed in this pull request?
1. Register CRD
2. Initialize informer and client for operate CRD
3. Filtering unset plugins
How was this patch tested?
1. make sandbox-build && make sandbox-run FLYTE_DEV=True
2. Installing crd opreators
image
3. make -C manager run
Labels
•
added: For new features.
This is important to improve the readability of release notes.
Setup process
1. Update complete.yaml
enabled_plugins:
tasks:
task-plugins:
enabled-plugins:
- container
- sidecar
- connector-service
- echo
- ray
- spark
- dask
- pytorch
- tensorflow
- mpi
default-for-task-types:
container: container
sidecar: sidecar
container_array: k8s-array
1. make devbox-start
2. Installing crd opreators
image
spark_role.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
name: spark
namespace: flyte
---
apiVersion:
rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: spark-testproject-development
roleRef:
apiGroup:
rbac.authorization.k8s.io
kind: ClusterRole
name: edit
subjects:
- kind: ServiceAccount
name: spark
namespace: flyte
Screenshots
1. spark
image
2. ray
image
3. dask
image
4. torch
image
Check all the applicable boxes
• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.
Related PRs
Docs link
•
main
•
#6583
•
[Flyte 7198] Enabling flyte plugins 👈
flyteorg/flyte