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

[QUESTION/HELP] Starting k3d with dual stack ipv6 enabled #1185

Open
mgazza opened this issue Dec 5, 2022 · 0 comments
Open

[QUESTION/HELP] Starting k3d with dual stack ipv6 enabled #1185

mgazza opened this issue Dec 5, 2022 · 0 comments
Labels
question Further information is requested

Comments

@mgazza
Copy link

mgazza commented Dec 5, 2022

Question / Where do you need Help?

Hi, I need instructions for getting dual stack ipv4/v6 enabled.

I have tried switching from flannel to calico which works however when providing --cluster-cidr and --service-cidr I receive an error.

WARN[0009] warning: encountered fatal log from node k3d-tilt-server-0 (retrying 9/10): �time="2022-12-05T16:01:24Z" level=fatal msg="cluster-cidr: [10.42.0.0/16 2c06:25:f1cd:11:10::/80] and node-ip: [172.25.0.3], must share the same IP version (IPv4, IPv6 or dual-stack)" 

then adding the following

      - arg: --node-ip=172.17.0.1,2c06:25:f1cd:11:50::20
        nodeFilters:
          - server:0

results in the agent giving the same error

WARN[0041] warning: encountered fatal log from node k3d-tilt-agent-0 (retrying 7/10): �time="2022-12-05T16:02:35Z" level=fatal msg="cluster-cidr: [10.42.0.0/16 2c06:25:f1cd:11:10::/80] and node-ip: [172.26.0.4], must share the same IP version (IPv4, IPv6 or dual-stack)" 

so adding the agent

      - arg: --node-ip=172.17.0.2,2c06:25:f1cd:11:50::21
        nodeFilters:
          - agent:0

and get the error

WARN[0940] warning: encountered fatal log from node k3d-tilt-agent-0 (retrying 0/10): <time="2022-12-05T16:19:05Z" level=fatal msg="Kubelet failed to wait for apiserver ready: timed out waiting for the condition, failed to get apiserver /readyz status: Get \"https://127.0.0.1:6444/readyz\": read tcp 127.0.0.1:43886->127.0.0.1:6444: read: connection reset by peer - error from a previous attempt: EOF" 

Scope of your Question

  • Is your question related to a specific version of k3d (or k3s)? no
    • Please paste the output of k3d version here
      k3d version v5.4.6
      k3s version v1.24.6-k3s1 (default)

related #833

@mgazza mgazza added the question Further information is requested label Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant