-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Additional Compute Machine Pools Rejected By Installer #1367
Comments
Not a 4.0 blocker for us, we already work around by filtering out non-worker pools when generating install config, and not doing so would be broken due to the restrictions around machine set node labels in 4.0. |
This is now fixed. Installer allows multiple machinepools /close |
@abhinavdahiya: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I still encounter the same problem as his. This is my version of the installer:
|
Version
Platform (aws|libvirt|openstack):
aws
What happened?
In #1231 support was added for additional compute machine sets, but validation is still blocking this.
FATAL failed to fetch Terraform Variables: failed to load asset "Install Config": invalid "install-config.yaml" file: compute[1].name: Unsupported value: "infra": supported values: "worker"
How to reproduce it (as minimally and precisely as possible)?
Install Config containing:
The text was updated successfully, but these errors were encountered: