-
Notifications
You must be signed in to change notification settings - Fork 16.4k
feat: K8S resource operator - CRD #35600
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
ef5a4ff to
dc2e476
Compare
43e0282 to
17ea599
Compare
potiuk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Do not know all the details but it does look good. to create the resources
Small NIT: @raphaelauv would be nice to have test_k8s_resource_iterator.py with a unit test for it - looks nicely unit-testable and we are eyeing to move things out of the list in test_proect_structure rather than add to the list.
|
@potiuk thanks for the review 👍 |
* feat: K8S resource operator - CRD * clean * tests * remove sensor ( for another PR ) * clean * test on k8s_resource_iterator
* feat: K8S resource operator - CRD * clean * tests * remove sensor ( for another PR ) * clean * test on k8s_resource_iterator
current K8S resource operators do not work with CRD
example rayjob of the kuberay operator and so on
this PR add support to airflow to create /
sensor/ delete CRD in K8S--
I will do another PR for the sensor