You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
terraform {
required_version=">= 0.12.0"
}
provider"aws" {
region=var.region
}
provider"random" {
version="~> 2.1"
}
provider"local" {
version="~> 1.2"
}
provider"null" {
version="~> 2.1"
}
provider"template" {
version="~> 2.1"
}
resource"random_string""suffix" {
length=8special=false
}
module"eks" {
source="../../../modules/aws/terraform-eks"env=local.envcluster_name=local.cluster_namecluster_version=1.14subnets=module.vpc.private_subnetsvpc_id=module.vpc.vpc_idworker_groups=[
{
name ="terraform-1"
instance_type ="t3.large"
key_name ="eks-dev"
bootstrap_extra_args ="--enable-docker-bridge true"
kubelet_extra_args ="--node-labels=env=Test,service=docker,team=platform"
node_group_k8s_labels = {
Environment ="Test"
Team ="Platform"
Service ="Docker"
}
asg_max_size ="0"# Maximum worker capacity in the autoscaling group.
asg_min_size ="0"
},
{
name ="admin-worker-group-1"
instance_type ="t3.xlarge"
key_name ="eks-dev"
bootstrap_extra_args ="--enable-docker-bridge true"
kubelet_extra_args ="--node-labels=env=Dev,service=ci-cd,team=platform"
node_group_k8s_labels = {
Environment ="Admin"
Team ="Platform"
}
asg_max_size ="10"# Maximum worker capacity in the autoscaling group.
asg_min_size ="1"
},
]
map_roles=var.map_rolesmap_users=var.map_users
}
Expected Behavior
As there are no changes made to terraform files or module, I should see no changes when I run plan.
Actual Behavior
I am getting changes for all of my worker groups when I run terraform plan. E.g. Below is the plan output for one of the worker group
# module.eks.aws_launch_configuration.workers[0] must be replaced+/-resource"aws_launch_configuration""workers" {
associate_public_ip_address=falseebs_optimized=trueenable_monitoring=trueiam_instance_profile="sennder-admin-cluster20200106121106098100000008"
~ id="sennder-admin-cluster-terraform-12020010612110773630000000d"-> (known after apply)
image_id="ami-07034b303e1ffc843"instance_type="t3.large"key_name="eks-dev"
~ name="sennder-admin-cluster-terraform-12020010612110773630000000d"-> (known after apply)
name_prefix="sennder-admin-cluster-terraform-1"security_groups=[
]
~ user_data_base64="BIG BLOCK OF BASE64"-> (known after apply) # forces replacement-vpc_classic_link_security_groups=[] ->null+ebs_block_device {
+delete_on_termination=(known after apply)
+device_name=(known after apply)
+encrypted=(known after apply)
+iops=(known after apply)
+no_device=(known after apply)
+snapshot_id=(known after apply)
+volume_size=(known after apply)
+volume_type=(known after apply)
}
~ root_block_device {
delete_on_termination=true
~ encrypted=false-> (known after apply)
iops=0volume_size=100volume_type="gp2"
}
}
# module.eks.random_pet.workers[0] must be replaced+/-resource"random_pet""workers" {
~ id="amusing-parakeet"-> (known after apply)
~ keepers={
-"lc_name" = "sennder-admin-cluster-terraform-12020010612110773630000000d"
} -> (known after apply) # forces replacementlength=2separator="-"
}
# module.eks.local_file.kubeconfig[0] must be replaced-/+resource"local_file""kubeconfig" {
~ content=""-> (known after apply) # forces replacementdirectory_permission="0777"file_permission="0777"filename="./kubeconfig_sennder-admin-cluster"
~ id="d2ea96f32318207ab27000f3d7ff80a70ae6b321"-> (known after apply)
}
Steps to Reproduce
terraform init
terraform plan
Additional Context
I found that this is happening for all the old clusters I am having.
The text was updated successfully, but these errors were encountered:
Krishna1408
changed the title
Terraform show changes for autoscaling group out of no where
Terraform show changes for launch configurations out of no where
Feb 12, 2020
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 1, 2020
This issue was closed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
Terraform Configuration Files
Expected Behavior
As there are no changes made to terraform files or module, I should see no changes when I run plan.
Actual Behavior
I am getting changes for all of my worker groups when I run terraform plan. E.g. Below is the plan output for one of the worker group
Steps to Reproduce
terraform init
terraform plan
Additional Context
I found that this is happening for all the old clusters I am having.
The text was updated successfully, but these errors were encountered: