-
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
Single/Multi-Namespace mode for helm chart #11034
Conversation
cc: @sjmiller609 |
kind: ClusterRole | ||
{{- else }} | ||
kind: Role |
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.
when you create a Role, you have to specify the namespace it belongs in.
ClusterRole, by contrast, is a non-namespaced resource.
https://kubernetes.io/docs/reference/access-authn-authz/rbac/
Can you add namespace?
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.
@mik-laj fixed 👍
Thanks for addressing this issue. I've also encountered this problem recently when I was creating an environment for multiple teams on one cluster. For now, I've added this option, but I think it's worth solving this problem.
|
# yamllint enable rule:line-length | ||
|
||
multiNamespaceMode: 'False' |
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.
Should we also update README.md? The minimum is updating the reference documentation, but I'd be happy if you would describe more about what "Multi namespace mode" means.
Reference documentation will be easier to maintain if validation for values.yml has been added.
#10664
Can you do rebase and update values.json? |
28f7520
to
3968395
Compare
@mik-laj rebased |
Can you add new item to values.schema.json? |
@mik-laj added |
Users should not REQUIRE a ClusterRole/ClusterRolebinding to run airflow via helm. This change will allow "single" and "multi" namespace modes so users can add airflow to managed kubernetes clusters
74d0e93
to
9753cb7
Compare
* Followup to apache#11034 * Was not referencing the correct kind of resources if multiNamespaceMode = False
* Followup to #11034 * Was not referencing the correct kind of resources if multiNamespaceMode = False
* Followup to apache#11034 * Was not referencing the correct kind of resources if multiNamespaceMode = False
* Multi-Namespace mode for helm chart Users should not REQUIRE a ClusterRole/ClusterRolebinding to run airflow via helm. This change will allow "single" and "multi" namespace modes so users can add airflow to managed kubernetes clusters * add namespace to role * add rolebinding too * add docs * add values.schema.json change (cherry picked from commit 93475e9)
* Multi-Namespace mode for helm chart Users should not REQUIRE a ClusterRole/ClusterRolebinding to run airflow via helm. This change will allow "single" and "multi" namespace modes so users can add airflow to managed kubernetes clusters * add namespace to role * add rolebinding too * add docs * add values.schema.json change (cherry picked from commit 93475e9)
* Multi-Namespace mode for helm chart Users should not REQUIRE a ClusterRole/ClusterRolebinding to run airflow via helm. This change will allow "single" and "multi" namespace modes so users can add airflow to managed kubernetes clusters * add namespace to role * add rolebinding too * add docs * add values.schema.json change (cherry picked from commit 93475e9)
* Multi-Namespace mode for helm chart Users should not REQUIRE a ClusterRole/ClusterRolebinding to run airflow via helm. This change will allow "single" and "multi" namespace modes so users can add airflow to managed kubernetes clusters * add namespace to role * add rolebinding too * add docs * add values.schema.json change (cherry picked from commit 93475e9)
* Multi-Namespace mode for helm chart Users should not REQUIRE a ClusterRole/ClusterRolebinding to run airflow via helm. This change will allow "single" and "multi" namespace modes so users can add airflow to managed kubernetes clusters * add namespace to role * add rolebinding too * add docs * add values.schema.json change (cherry picked from commit 93475e9)
* Followup to apache#11034 * Was not referencing the correct kind of resources if multiNamespaceMode = False (cherry picked from commit 3391c90)
Users should not REQUIRE a ClusterRole/ClusterRolebinding
to run airflow via helm. This change will allow "single" and "multi"
namespace modes so users can add airflow to managed kubernetes clusters
^ 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.