Skip to content
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

Self-managed Node Group example node fails to join cluster #2983

Closed
1 task done
RyanTimoney opened this issue Mar 21, 2024 · 2 comments
Closed
1 task done

Self-managed Node Group example node fails to join cluster #2983

RyanTimoney opened this issue Mar 21, 2024 · 2 comments

Comments

@RyanTimoney
Copy link

RyanTimoney commented Mar 21, 2024

Description

I've cloned the repo at 70866e6, commented out lines 75-302 within examples/self_managed_node_group/main.tf (this is the content within self_managed_nod_groups except for default_node_group = {}) and applied it. coredns fails to deploy and the one node that is created does not join the cluster.

  • ✋ I have searched the open/closed issues and my issue is not listed.

Versions

  • Module version [Required]: 20.8.4 (this also fails on 20.8.3)
  • Terraform version: 1.7.5
  • Provider version(s):
Terraform v1.7.5
on darwin_amd64
+ provider registry.terraform.io/hashicorp/aws v5.41.0
+ provider registry.terraform.io/hashicorp/cloudinit v2.3.3
+ provider registry.terraform.io/hashicorp/null v3.2.2
+ provider registry.terraform.io/hashicorp/time v0.11.1
+ provider registry.terraform.io/hashicorp/tls v4.0.5

Reproduction Code [Required]

  1. Clone the repo at 70866e6
  2. CD to examples/self_managed_node_group
  3. Within main.tf, comment out lines 75-302. Within the self_managed_node_groups map, only default_node_group = {} will remain.
  4. terraform init
  5. terraform apply
  • No workspace
  • No cache
  • This was in an empty AWS region. No custom VPC was present.
  • I've got AdministratorAccess within this account

Expected behavior

CoreDNS installs successfully and the node joins the cluster.

Actual behavior

After 20 minutes, this error is thrown:

╷
│ Warning: Running terraform apply again will remove the kubernetes add-on and attempt to create it again effectively purging previous add-on configuration
│
│   with module.eks.aws_eks_addon.this["coredns"],
│   on ../../main.tf line 492, in resource "aws_eks_addon" "this":
│  492: resource "aws_eks_addon" "this" {
│
╵
╷
│ Error: waiting for EKS Add-On (ex-self-managed-node-group:coredns) create: timeout while waiting for state to become 'ACTIVE' (last state: 'DEGRADED', timeout: 20m0s)
│
│   with module.eks.aws_eks_addon.this["coredns"],
│   on ../../main.tf line 492, in resource "aws_eks_addon" "this":
│  492: resource "aws_eks_addon" "this" {
│
╵

While the Auto Scaling Group is created with what seems to be appropriate tags, no nodes join the cluster.

$ k get pods --all-namespaces
NAMESPACE     NAME                       READY   STATUS    RESTARTS   AGE
kube-system   coredns-68bd859788-dh994   0/1     Pending   0          39m
kube-system   coredns-6cbc78c9f9-7k4kn   0/1     Pending   0          36m
kube-system   coredns-6cbc78c9f9-st7l2   0/1     Pending   0          36m

$ k get nodes
No resources found

$ k auth can-i list nodes
Warning: resource 'nodes' is not namespace scoped

yes
Copy link

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Apr 25, 2024
Copy link

github-actions bot commented May 5, 2024

This issue was automatically closed because of stale in 10 days

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants