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
I am using a CF template to manage EKS Node Groups. When I pass --use-max-pods=false into the BootstrapArguments parameter, it appears to be ignored by the bootstrap.sh script, or some other component as there is still a limit being applied to each node.
Reproduction Steps
Pass --use-max-pods=false into the BootstrapArguments parameter of a CF template.
Error Log
No error. The nodes still have a pods entry in the allocatable section of their configuration when I interrogate with kubectl get nodes -o yaml.
Environment
CLI Version : 1.16.188
Framework Version: not sure - which framework?
OS : MacOS
Language : of what?
Other
Looks to be a duplicate of #4752 which should have been fixed in #4753?
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered:
Hi @tomkivlin, you are right this is a duplicate and the issue was fixed and merged yesterday. There hasn't been a new release yet with those changes so that's why you're still experiencing this issue unfortunately. The new release should be out in a few days.
I will close this issue. Feel free to reopen if once you get the new release you still encounter some problems.
I am using a CF template to manage EKS Node Groups. When I pass
--use-max-pods=false
into theBootstrapArguments
parameter, it appears to be ignored by the bootstrap.sh script, or some other component as there is still a limit being applied to each node.Reproduction Steps
Pass
--use-max-pods=false
into theBootstrapArguments
parameter of a CF template.Error Log
No error. The nodes still have a
pods
entry in theallocatable
section of their configuration when I interrogate withkubectl get nodes -o yaml
.Environment
Other
Looks to be a duplicate of #4752 which should have been fixed in #4753?
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: