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

AWS classic loadbalancer is not cleaned on apply #68605

Open
matti opened this Issue Sep 13, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@matti

matti commented Sep 13, 2018

/kind bug

What happened:

Applied this in AWS:

kind: Service
apiVersion: v1
metadata:
  namespace: lolcats
spec:
  type: LoadBalancer
...

---> got a classic loadbalancer.

Changed to this

kind: Service
apiVersion: v1
metadata:
  namespace: lolcats
  annotations:
    service.beta.kubernetes.io/aws-load-balancer-type: "nlb"
spec:
  type: LoadBalancer
...

And after apply got an NLB, but the classic loadbalancer is still there.

What you expected to happen:

Not to get billed by AWS for $20/month for nothing

Environment:

  • Kubernetes version (use kubectl version): 1.11.1
  • Cloud provider or hardware configuration: aws
  • OS (e.g. from /etc/os-release): coreos
  • Kernel (e.g. uname -a): stable
  • Install tools: kontena pharos
  • Others: beer
@matti

This comment has been minimized.

Show comment
Hide comment
@matti

matti Sep 13, 2018

/sig cloud-provider

matti commented Sep 13, 2018

/sig cloud-provider

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment