Closed hamc closed 3 years ago
See #10961.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Has this one been resolved now?
Thanks
/close /remove-lifecycle stale
@olemarkus: Closing this issue.
1. What
kops
version are you running? The commandkops version
, will display this information.1.19.0
2. What Kubernetes version are you running?
kubectl version
will print the version if a cluster is running or provide the Kubernetes version specified as akops
flag.1.19.7
3. What cloud provider are you using?
AWS
4. What commands did you run? What is the simplest way to reproduce this issue?
kops update cluster
5. What happened after the commands executed?
It removes the Classical Load Balancer from the AutoScaling Group even when the
.spec.api.loadBalancer.class
option is set to Classic.6. What did you expect to happen?
As we were unable to use NLB in conjunction with the spotinst, we would like to continue using CLB. The kops should keep the LoadBalancer configuration of the Autoscaling Group when using the
Classic
option for.spec.api.loadBalancer.class
.7. Please provide your cluster manifest. Execute
kops get --name my.example.com -o yaml
to display your cluster manifest. You may want to remove your cluster name and other sensitive information.8. Please run the commands with most verbose logging by adding the
-v 10
flag. Paste the logs into this report, or in a gist and provide the gist link here.9. Anything else do we need to know?