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
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Feature Request
One thing I've started to see the need for is to apply custom flags to the kube components that may not necessarily be kargo defaults. We kind of do something similar to this with docker options, but I'd like to see it extended.
A good use case:
As we've started building lots of different, decently sized clusters, we've noticed that we are all of a sudden hitting AWS API limits all over the place. It prevents volumes from attaching, as well as non-k8s users from doing things in AWS. A bug was filed to support this, but it involved adding a new flag to designate the timing between API calls. All good, but there's really no way for me to set this at deploy time I don't think. Plus, I don't think it's a hard requirement for all AWS users who might be trying kargo, as it only surfaces at a certain scale.
I could also see this being useful as we get further along down our at-scale testing to be able to set custom kubelet pod eviction flags and stuff.
The text was updated successfully, but these errors were encountered:
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Feature Request
One thing I've started to see the need for is to apply custom flags to the kube components that may not necessarily be kargo defaults. We kind of do something similar to this with docker options, but I'd like to see it extended.
A good use case:
As we've started building lots of different, decently sized clusters, we've noticed that we are all of a sudden hitting AWS API limits all over the place. It prevents volumes from attaching, as well as non-k8s users from doing things in AWS. A bug was filed to support this, but it involved adding a new flag to designate the timing between API calls. All good, but there's really no way for me to set this at deploy time I don't think. Plus, I don't think it's a hard requirement for all AWS users who might be trying kargo, as it only surfaces at a certain scale.
I could also see this being useful as we get further along down our at-scale testing to be able to set custom kubelet pod eviction flags and stuff.
The text was updated successfully, but these errors were encountered: