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
Although MINIMUM_IP_TARGET have been documented, but there have no explanation what's the relationship between MINIMUM_IP_TARGET and --minimum-ip-target / --windows-minimum-ip-target? besides, it may need to explain why minimum-ip-target would pointed to minimumWindowsIPTarget variable as well.
Why is this needed:
Tried to study where the minimum-ip-target inside configmaps/amazon-vpc-cni came from, and I can see it's defined by minimumWindowsIPTarget under values.yaml
After few minutes code tracing, I found it was initially introduced by PR#2715, but no explanation for why minimum-ip-target would initially pointed to minimumWindowsIPTarget ? I though it should be windows-minimum-ip-target?
Later on, I can see PR#2716 changed its default to 3, but still no explanation for why the default value changed?
What would you like to be added:
Although
MINIMUM_IP_TARGET
have been documented, but there have no explanation what's the relationship betweenMINIMUM_IP_TARGET
and--minimum-ip-target / --windows-minimum-ip-target
? besides, it may need to explain whyminimum-ip-target
would pointed tominimumWindowsIPTarget
variable as well.Why is this needed:
Tried to study where the
minimum-ip-target
insideconfigmaps/amazon-vpc-cni
came from, and I can see it's defined byminimumWindowsIPTarget
undervalues.yaml
amazon-vpc-cni-k8s/charts/aws-vpc-cni/templates/configmap.yaml
Lines 19 to 26 in 110c30d
amazon-vpc-cni-k8s/charts/aws-vpc-cni/values.yaml
Lines 119 to 123 in 110c30d
After few minutes code tracing, I found it was initially introduced by PR#2715, but no explanation for why
minimum-ip-target
would initially pointed tominimumWindowsIPTarget
? I though it should bewindows-minimum-ip-target
?Later on, I can see PR#2716 changed its default to
3
, but still no explanation for why the default value changed?I'm aware of the variables renamed at aws/amazon-vpc-resource-controller-k8s,
but it looks like the variable names does not reflect to what it should be.
Proposed change
templates/configmap.yaml
values.yaml
The text was updated successfully, but these errors were encountered: