No nodes found after EKS stake created successfully, v3.0.0

[brant4test]

I have issues

No nodes found after EKS stake created successfully, v3.0.0

I'm submitting a...

bug report

• feature request
• support request
• kudos, thank you, warm fuzzy

What is the current behavior?

$ terraform apply
...
Apply complete! Resources: 54 added, 0 changed, 0 destroyed.

$ kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-66bb8d6fdc-s4jcg 0/1 Pending 0 3m42s
kube-system coredns-66bb8d6fdc-z9d8k 0/1 Pending 0 3m42s

$ kubectl get nodes -owide
No resources found.

If this is a bug, how to reproduce? Please include a code sample if relevant.

Updated contents
$ vi main.tf

  worker_groups = [
    {
      # This will launch an autoscaling group with only On-Demand instances
      name                 = "worker_group_od"
      instance_type        = "t2.small"
      additional_userdata  = "sudo sysctl -w vm.max_map_count=262144;sudo sed -i -e 's,allow-privileged=true,allow-privileged=true --read-only-port 10255 --cadvisor-port=4194,' /etc/systemd/system/kubelet.service;sudo systemctl daemon-reload;sudo systemctl restart kubelet"
      subnets              = "${join(",", module.vpc.private_subnets)}"
      asg_desired_capacity = 1
      asg_max_size         = 1
      asg_min_size         = 1
      root_volume_size     = "50"
      root_volume_type     = "gp2"
      root_iops            = "0"
      key_name             = "eks-key"
      autoscaling_enabled  = true
      protect_from_scale_in= true
      placement_group      = ""
    },
  ]
  worker_groups_launch_template = [
    {
      # This will launch an autoscaling group with only Spot Fleet instances
      name                                     = "workers_group_launch_template_spot"
      instance_type                            = "${var.instance_type}"
      additional_userdata                      = "sudo sysctl -w vm.max_map_count=262144;sudo sed -i -e 's,allow-privileged=true,allow-privileged=true --read-only-port 10255 --cadvisor-port=4194,' /etc/systemd/system/kubelet.service;sudo systemctl daemon-reload;sudo systemctl restart kubelet"
      subnets                                  = "${join(",", module.vpc.private_subnets)}"
      additional_security_group_ids            = "${aws_security_group.worker_group_mgmt_one.id},${aws_security_group.worker_group_mgmt_two.id}"
      override_instance_type                   = "t2.large"
      asg_desired_capacity                     = "${var.asg_desired_capacity}"
      asg_max_size                             = "${var.asg_max_size}"
      asg_min_size                             = "${var.asg_min_size}"
      spot_instance_pools                      = 10
      spot_max_price                           = ""
      spot_allocation_strategy                 = "lowest-price"
      spot_instance_pools                      = 10
      on_demand_percentage_above_base_capacity = "0"
      root_volume_size     = "50"
      root_volume_type     = "gp2"
      root_iops            = "0"
      key_name             = "eks-key"
      autoscaling_enabled  = true
      protect_from_scale_in= true
      root_encrypted       = false
      placement_group      = ""
    },

What's the expected behavior?

Are you able to fix this problem and submit a PR? Link here if you have already.

Environment details

• Affected module version: v3.0.0
• OS: Amazon EKS-optimized AMI, by default
• Terraform version: v0.11.13

• provider.aws v2.8.0
• provider.local v1.2.1
• provider.null v2.1.1
• provider.random v1.3.1
• provider.template v2.1.1

Any other relevant info

Kubernetes Version: 1.12.6
Amazon EKS Platform Version: eks.1

[brant4test]

The cAdvisor port, which exposed the raw cAdvisor UI & API was removed in Kubernetes 1.12

Apr 28 10:57:26 ip-10-250-206-49.ec2.internal kubelet[22120]: --cpu-manager-policy string                                                                                 CPU Manager policy to use. Possible values: 'none', 'static'. Default: 'none' (default "none") (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.)
Apr 28 10:57:26 ip-10-250-206-49.ec2.internal kubelet[22120]: --cpu-cfs-quota-period duration                                                                             Sets CPU CFS quota period value, cpu.cfs_period_us, defaults to Linux Kernel default (default 100ms) (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.)
Apr 28 10:57:26 ip-10-250-206-49.ec2.internal systemd[1]: kubelet.service failed.
Apr 28 10:57:26 ip-10-250-206-49.ec2.internal kubelet[22120]: --cpu-cfs-quota                                                                                             Enable CPU CFS quota enforcement for containers that specify CPU limits (default true) (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.)
Apr 28 10:57:26 ip-10-250-206-49.ec2.internal kubelet[22120]: --contention-profiling                                                                                      Enable lock contention profiling, if profiling is enabled (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.)
Apr 28 10:57:26 ip-10-250-206-49.ec2.internal kubelet[22120]: --containerized                                                                                             Running kubelet in a container.
Apr 28 10:57:26 ip-10-250-206-49.ec2.internal kubelet[22120]: --containerd string                                                                                         containerd endpoint (default "unix:///var/run/containerd.sock") (DEPRECATED: This is a cadvisor flag that was mistakenly registered with the Kubelet. Due to legacy concerns, it will follow the standard CLI deprecation timeline before being removed.)
Apr 28 10:57:26 ip-10-250-206-49.ec2.internal kubelet[22120]: --container-runtime-endpoint string                                                                         [Experimental] The endpoint of remote runtime service. Currently unix socket is supported on Linux, and tcp is supported on windows.  Examples:'unix:///var/run/dockershim.sock', 'tcp://localhost:3735' (default "unix:///var/run/dockershim.sock")
Apr 28 10:57:26 ip-10-250-206-49.ec2.internal systemd[1]: Unit kubelet.service entered failed state.
Apr 28 10:57:26 ip-10-250-206-49.ec2.internal kubelet[22120]: --container-runtime string                                                                                  The container runtime to use. Possible values: 'docker', 'remote', 'rkt (deprecated)'. (default "docker")
Apr 28 10:57:26 ip-10-250-206-49.ec2.internal kubelet[22120]: --container-log-max-size string                                                                             <Warning: Beta feature> Set the maximum size (e.g. 10Mi) of container log file before it is rotated. This flag can only be used with --container-runtime=remote. (default "10Mi") (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.)
Apr 28 10:57:26 ip-10-250-206-49.ec2.internal kubelet[22120]: --container-log-max-files int32                                                                             <Warning: Beta feature> Set the maximum number of container log files that can be present for a container. The number must be >= 2. This flag can only be used with --container-runtime=remote. (default 5) (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.)
Apr 28 10:57:26 ip-10-250-206-49.ec2.internal kubelet[22120]: --container-hints string                                                                                    location of the container hints file (default "/etc/cadvisor/container_hints.json") (DEPRECATED: This is a cadvisor flag that was mistakenly registered with the Kubelet. Due to legacy concerns, it will follow the standard CLI deprecation timeline before being removed.)
Apr 28 10:57:26 ip-10-250-206-49.ec2.internal kubelet[22120]: --config string                                                                                             The Kubelet will load its initial configuration from this file. The path may be absolute or relative; relative paths start at the Kubelet's current working directory. Omit this flag to use the built-in default configuration values. Command-line flags override configuration from this file.
Apr 28 10:57:26 ip-10-250-206-49.ec2.internal systemd[1]: kubelet.service: main process exited, code=exited, status=255/n/a

[github-actions]

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.