-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
All k8s object must comply with JSON Schema #12003
Conversation
CC: @FloChehab |
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.
❤️ - this is what switching to pytest-based tests for k8s enabled
The PR should be OK to be merged with just subset of tests as it does not modify Core of Airflow. The committers might merge it or can add a label 'full tests needed' and re-run it to run all tests if they see it is needed! |
* All k8s resources should have global labels * All k8s object must comply with JSON Schema
Followup to apache#12003: * Some network policies & ingress are not valid against the jsonschema (empty values mostly) * Some network policies conditionnal definitions were incorrect
* All k8s resources should have global labels * All k8s object must comply with JSON Schema (cherry picked from commit 3c85c2c)
* All k8s resources should have global labels * All k8s object must comply with JSON Schema (cherry picked from commit 3c85c2c)
* All k8s resources should have global labels * All k8s object must comply with JSON Schema (cherry picked from commit 3c85c2c)
* All k8s resources should have global labels * All k8s object must comply with JSON Schema (cherry picked from commit 3c85c2c)
Followup to apache#12003: * Some network policies & ingress are not valid against the jsonschema (empty values mostly) * Some network policies conditionnal definitions were incorrect
* Fix chart network policies definion and compliance Followup to #12003: * Some network policies & ingress are not valid against the jsonschema (empty values mostly) * Some network policies conditionnal definitions were incorrect * Support external redis instance in helm chart The main objective here is to support the use of an external redis instance in the helm chart. The values 'data.brokerUrl' and 'data.brokerUrlSecretName' are added and templates are updated. This support is added with no breaking changes (hopefully); only the redis.brokerURLSecretName value is removed, but it wasn't actually used in the chart. Extensive tests for the redis related part of this chart are also added (including runtime checks on the values). Docs also updated. Closes #11705
* Fix chart network policies definion and compliance Followup to #12003: * Some network policies & ingress are not valid against the jsonschema (empty values mostly) * Some network policies conditionnal definitions were incorrect * Support external redis instance in helm chart The main objective here is to support the use of an external redis instance in the helm chart. The values 'data.brokerUrl' and 'data.brokerUrlSecretName' are added and templates are updated. This support is added with no breaking changes (hopefully); only the redis.brokerURLSecretName value is removed, but it wasn't actually used in the chart. Extensive tests for the redis related part of this chart are also added (including runtime checks on the values). Docs also updated. Closes #11705 (cherry picked from commit 809ddcd)
* All k8s resources should have global labels * All k8s object must comply with JSON Schema (cherry picked from commit 3c85c2c)
* All k8s resources should have global labels * All k8s object must comply with JSON Schema Partial Commit Extracted From: https://github.com/apache/airflow
Depends on: https://github.com/apache/airflow/pull/12002/files
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.