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

feat: Test ipv6 example #1584

Conversation

csantanapr
Copy link
Contributor

test ipv6 example

Signed-off-by: Carlos Santana <csantana23@gmail.com>
@csantanapr csantanapr requested a review from a team as a code owner May 5, 2023 02:17
Signed-off-by: Carlos Santana <csantana23@gmail.com>
@csantanapr csantanapr changed the title test ipv6 example feat: Test ipv6 example May 5, 2023
@csantanapr csantanapr marked this pull request as draft May 5, 2023 03:31
@csantanapr
Copy link
Contributor Author

@bryantbiggs
Could you take a look? the node group doesn't join with ipv6 enabled

Error on apply is

│ Error: waiting for EKS Node Group (ipv6-eks-cluster:initial-2023050502340400550000000f) to create: unexpected state 'CREATE_FAILED', wanted target 'ACTIVE'. last error: 1 error occurred:
│       * i-0513204761ba0c3a3, i-05d8e220a99592cf3: NodeCreationFailure: Instances failed to join the kubernetes cluster
│ 
│ 
│ 
│   with module.eks.module.eks_managed_node_group["initial"].aws_eks_node_group.this[0],
│   on .terraform/modules/eks/modules/eks-managed-node-group/main.tf line 308, in resource "aws_eks_node_group" "this":
│  308: resource "aws_eks_node_group" "this" {
│ 

@bryantbiggs bryantbiggs marked this pull request as ready for review May 22, 2023 12:31
@bryantbiggs
Copy link
Contributor

@csantanapr are we ok to merge this or are there additional changes to be made/added?

@csantanapr
Copy link
Contributor Author

@bryantbiggs thanks for the update, I did some reading on ipv6 and I understand now why the egress only ipv6 was need it .
Everything is working now, all pods ipv6

NAMESPACE     NAME                       READY   STATUS    RESTARTS   AGE   IP                                       NODE                                        NOMINATED NODE   READINESS GATES
default       nginx-748c667d99-8f5rn     1/1     Running   0          16m   2600:1f14:237:6303:1a0d::                ip-10-0-4-47.us-west-2.compute.internal     <none>           <none>
kube-system   aws-node-nbjcg             1/1     Running   0          39m   2600:1f14:237:6303:49c4:4d1a:2f64:d97e   ip-10-0-4-47.us-west-2.compute.internal     <none>           <none>
kube-system   aws-node-rbcdl             1/1     Running   0          39m   2600:1f14:237:6305:688:e45c:e1a5:266f    ip-10-0-37-245.us-west-2.compute.internal   <none>           <none>
kube-system   coredns-6c45d94f67-dmbf2   1/1     Running   0          46m   2600:1f14:237:6305:219b::1               ip-10-0-37-245.us-west-2.compute.internal   <none>           <none>
kube-system   coredns-6c45d94f67-jm7qc   1/1     Running   0          46m   2600:1f14:237:6305:219b::                ip-10-0-37-245.us-west-2.compute.internal   <none>           <none>
kube-system   kube-proxy-rtv5q           1/1     Running   0          40m   2600:1f14:237:6303:49c4:4d1a:2f64:d97e   ip-10-0-4-47.us-west-2.compute.internal     <none>           <none>
kube-system   kube-proxy-zhrbp           1/1     Running   0          40m   2600:1f14:237:6305:688:e45c:e1a5:266f    ip-10-0-37-245.us-west-2.compute.internal   <none>           <none>

@csantanapr csantanapr merged commit 10ee0fd into aws-ia:refactor/addons-module May 22, 2023
bryantbiggs pushed a commit that referenced this pull request Jun 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants