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

Propose a request to add a feature to Self managed Airflow #545

Open
sayakin0519 opened this issue Jun 3, 2024 · 1 comment
Open

Propose a request to add a feature to Self managed Airflow #545

sayakin0519 opened this issue Jun 3, 2024 · 1 comment
Labels

Comments

@sayakin0519
Copy link

Hi @jagpk it's been a long time.

I've reviewed the answer you gave me on LinkedIn.

I've written what you asked me to leave here.

First.
The current version doesn't have Karpenter's functionality, can it be added?
And can Karpenter be extended to Airflow environments on existing instances of
into an existing instance of Airflow?

This would include things like Airflow login policies, GCP and AWS account authentication, etc.
automatically replicated.

It would also be nice to see an example of using the security key storage feature provided by AWS.
(AWS key management service)

Second.
K8s' node selector and Karpenter work together to provide a structure that is part of the
to the selected node when scaling. Is it possible to add this feature?
(I want the node running the worker pod to be the one that scales).

Third.
It would be nice to have a benchmark to test the deployed workload environment
(AWS products or third-party would be great, or a way to do it in the docs).

Thanks.

Copy link
Contributor

github-actions bot commented Jul 4, 2024

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant