You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: