Skip to content
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

Provide access privilege required for cncf.kubernetes operators/executors #40210

Open
1 of 2 tasks
pykenny opened this issue Jun 13, 2024 · 2 comments
Open
1 of 2 tasks

Comments

@pykenny
Copy link

pykenny commented Jun 13, 2024

What do you see as an issue?

In cncf-kubernetes provider's operator section, it describes how each operator work, but does not mention what type of access privileges are required to run these operators.

Same kind of details may be needed for the two types of Kubernetes executors as well.

Solving the problem

Provide privileges on Kubernetes resource required for each operator.

For instance, in 3rd-party airflow_kubernetes_job_operator package, it lists out all the privileges needed to gain full functionality of their operator in readme, written in RBAC format:

Anything else

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@pykenny pykenny added kind:bug This is a clearly a bug kind:documentation needs-triage label for new issues that we didn't triage yet labels Jun 13, 2024
@potiuk potiuk added good first issue and removed kind:bug This is a clearly a bug labels Jun 13, 2024
@potiuk
Copy link
Member

potiuk commented Jun 13, 2024

Sure. Marked it as good-first-issue and you are free to contribute it, otherwise it will have to wait for someone to volunteer, pick it up and contribute.

@potiuk potiuk removed the needs-triage label for new issues that we didn't triage yet label Jun 13, 2024
@topherinternational
Copy link
Contributor

@pykenny A good start might be the k8s permissions in the Helm chart, e.g. https:/apache/airflow/blob/providers-cncf-kubernetes/8.3.4/chart/templates/rbac/pod-launcher-role.yaml (and others in that directory).

It's not exactly the k8s operators, but it should be a similar perms profile as what is needed to launch a task pod from the k8s executor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants