Skip to content

test skipper-ingress with eks karpenter ipv6 with hostNetwork and hostPort #9637

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.

Sign up for GitHub

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

Jump to bottom
Draft
wants to merge 15 commits into
base: dev
Choose a base branch
from
Draft

test skipper-ingress with eks karpenter ipv6 with hostNetwork and hostPort #9637

wants to merge 15 commits into from

Conversation

ayruslore
Copy link
Collaborator

Test PR

Testing skipper ingress on eks with karpenter ipv6

With AWSCNI enabled and hostNetwork and hostPort enabled

test skipper-ingress with eks karpenter ipv6 with hostNetwork and hos…
39b8e6a 
…tPort

Signed-off-by: speruri <surya.srikar.peruri@zalando.de>
@ayruslore ayruslore added the minor Minor changes, e.g. low risk config updates, changes that do not introduce a new API call. label Jul 3, 2025
speruri added 9 commits July 15, 2025 01:48
use latest controller image
e0a6232 
Signed-off-by: speruri <surya.srikar.peruri@zalando.de>
Merge remote-tracking branch 'origin/dev' into test/skipper-with-eks-…
0f4a99d 
…karpenter--ipv6-host
remove dual stack and try
42b3656
use an amd image
8a5e868 
Signed-off-by: speruri <surya.srikar.peruri@zalando.de>
use multiarch image from the controller
54281ab
use gwproxy namespace image
8d7f00c 
Signed-off-by: speruri <surya.srikar.peruri@zalando.de>
use teapot namespace itself
6e00ee8 
Signed-off-by: speruri <surya.srikar.peruri@zalando.de>
use only multiarch image
cd8c4a8 
Signed-off-by: speruri <surya.srikar.peruri@zalando.de>
change target type ip to dual stack
1476406 
Signed-off-by: speruri <surya.srikar.peruri@zalando.de>
@ayruslore ayruslore mentioned this pull request Jul 18, 2025
Draft
speruri added 3 commits July 18, 2025 12:30
Merge remote-tracking branch 'origin/dev' into test/skipper-with-eks-…
8c9b149 
…karpenter--ipv6-host
use the vendored-in support for targetgroup ipv6
c528bbe 
Signed-off-by: speruri <surya.srikar.peruri@zalando.de>
enable loadbalancer dualstack
6d134a2 
Signed-off-by: speruri <surya.srikar.peruri@zalando.de>
@ayruslore
Copy link
Collaborator Author

We need the load balancer ip address type to be dual stack so that we can add ipv6 target groups.

See error message from cf stack

This AWS::ElasticLoadBalancingV2::Listener resource is in a UPDATE_FAILED state.

Resource handler returned message: "You cannot associate an IPv6 target group with a load balancer that has an 'ipv4' IP 
address type (Service: ElasticLoadBalancingV2, Status Code: 400, Request ID: 1c8e8ce0-eefa-4ae4-b61a-95e72bca5812) 
(SDK Attempt Count: 1)" (RequestToken: ced9b7e0-78da-123f-803d-f48404feb18c, HandlerErrorCode: InvalidRequest)

speruri added 2 commits July 18, 2025 12:59
use dual stack nlbs
094d216 
Signed-off-by: speruri <surya.srikar.peruri@zalando.de>
extend controller permissions to describe peering vpc connections
6658492 
Signed-off-by: speruri <surya.srikar.peruri@zalando.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
minor Minor changes, e.g. low risk config updates, changes that do not introduce a new API call.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@ayruslore