Always use eksStatus for security groups

rancher/rancher#28148
This commit is contained in:
Westly Wright 2020-07-30 10:05:05 -07:00
parent 33040bd83b
commit 010f8a9e74
No known key found for this signature in database
GPG Key ID: 4FAB3D8673DC54A3
2 changed files with 11 additions and 4 deletions

View File

@ -329,6 +329,10 @@
<div>
{{sub}}
</div>
{{else}}
<div>
{{t "clusterNew.amazoneks.subnet.noneSelected"}}
</div>
{{/each}}
</div>
{{/if}}
@ -338,7 +342,10 @@
{{#if (eq step 3)}}
<SaveCancel
@editing={{eq mode "edit"}}
@saveDisabled={{and (eq vpcSubnetMode "custom") (lte selectedSubnets.length 1)}}
@saveDisabled={{and
(eq vpcSubnetMode "custom")
(lte selectedSubnets.length 1)
}}
@save={{action "setSubnets"}}
@cancel={{close}}
@createLabel="clusterNew.amazoneks.subnet.next"
@ -374,9 +381,8 @@
</option>
{{/each}}
</select>
{{else if
(or config.securityGroups primaryResource.eksStatus.securityGroups)}}
{{#each config.securityGroups as |sg|}}
{{else}}
{{#each primaryResource.eksStatus.securityGroups as |sg|}}
<div>
{{sg}}
</div>

View File

@ -3407,6 +3407,7 @@ clusterNew:
help: EKS requires at least 2 subnets. Subnets should span at least 2 availability zones.
next: "Next: Select Security Group"
loading: "Loading Security Groups from Amazon..."
noneSelected: "Rancher created VPC, Subnet, and Securty Group"
associateWorkerNodePublicIp:
title: Public IP for Worker Nodes
radio: