-
Notifications
You must be signed in to change notification settings - Fork 3k
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
RKE2 Cluster Templates: Some fields (i.e. ec2 rootSize
) need to be wrapped in quotes, otherwise an error is thrown
#40128
Comments
rootSize
need to be wrapped in quotes, otherwise an error is thrownrootSize
) need to be wrapped in quotes, otherwise an error is thrown
@slickwarren Are you using https://github.com/slickwarren/cluster-template-examples repo |
I was using @StrongMonkey 's chart. Would the default value in questions.yaml not being a string, even though the default type is |
So values missing the |
ah, I see it now in the values-aws.yaml. However, I just checked the request sent when provisioning an RKE2 cluster using the node driver (not template) and it does not have a |
@slickwarren Where are we with this? What is the cluster template git repo that you are using that has the problem? I tried the https://github.com/StrongMonkey/cluster-template-example but this does not presents form to edit |
@nwmac it should be available there https://github.com/StrongMonkey/cluster-template-examples , use branch |
@slickwarren This does not appear to be a UI issue. |
I believe this issue should be transferred to the back end. This seems to be an issue with Helm. As Neill noted above, the UI always sends the value as a string regardless of whether it is wrapped in quotes or not. But that value is then passed to Helm, which converts it to an integer when there are no letters in it. helm/helm#1694 I'm pretty sure a small PR to the cluster template repo (https://github.com/rancher/cluster-template-examples) ought to force Helm to keep the value in string format, but I didn't figure out exactly how to do it. In the helm chart values.yaml, I tried wrapping the value in quotes like this:
and like this:
But neither worked. In any case, it's probably more of a matter for the back end. |
Transferring to backend. @Jono-SUSE-Rancher this isn't a high priority, barring anything that QA brings up, but it's a solid tech debt issue to consider. This should be able to leverage form usage in other parts of Helm chart validation. |
on 2.6.0-rc1:
When provisioning using a cluster template, the
rootSize
for aws EC2 provisioners does not currently take an integer when it should. Instead an error is thrown when the below is used.wrapping the number i.e.
"16"
is a workaround for this issue.repro steps:
nodepools
ensure that therootSize
option has an integer valueThe text was updated successfully, but these errors were encountered: