aws creating new instances when I terminate an existing instance

+1 vote
I have an existing kubernetes cluster. The problem is after my work got done, I had terminated the instance but a new instance automatically got created and when I terminated another instance got created. I havent created a loadbalancer either. The main issue is the new instances that are being created are t2.medium and c4.large which not the free tier ones. I really want these instances as they are going to charge me a lot.

Thank you..
Oct 24, 2018 in Kubernetes by Hannah
• 18,520 points
673 views

1 answer to this question.

0 votes
Hey @Hannah, Check if the autoscaling is initiated. Most of the times autoscaling is initiated by default when you create the cluster, delete it immediately. Even I had the same issue, all the best for the time you get your aws bill.. hahah..
answered Oct 24, 2018 by Kalgi
• 52,350 points

Related Questions In Kubernetes

0 votes
2 answers

NoSuchBucket error when running Kubernetes on AWS

It was a bug on their part. ...READ MORE

answered Sep 4, 2018 in Kubernetes by Nilesh
• 7,060 points
980 views
0 votes
1 answer

image can't be pulled error when I try to pull a docker image - kubernetes

I think the image is being pulled ...READ MORE

answered Sep 4, 2018 in Kubernetes by Kalgi
• 52,350 points
6,256 views
0 votes
1 answer

permissions related to AWS ECR

if you add allowContainerRegistry: true, kops will add those permissions ...READ MORE

answered Oct 9, 2018 in Kubernetes by Kalgi
• 52,350 points
1,434 views
+1 vote
1 answer
0 votes
1 answer
0 votes
1 answer

“403 Insufficient Permission” while creating a Kubernetes Cluster on Google Cloud instance

To run ./cluster/kube-up.sh, you most likely need compute scope ...READ MORE

answered Aug 28, 2018 in Kubernetes by Kalgi
• 52,350 points
1,345 views
webinar REGISTER FOR FREE WEBINAR X
REGISTER NOW
webinar_success Thank you for registering Join Edureka Meetup community for 100+ Free Webinars each month JOIN MEETUP GROUP