<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!

Before creating an issue, make sure you've checked the following:

• You are running the latest released version of k0s
• Make sure you've searched for existing issues, both open and closed
• Make sure you've searched for PRs too, a fix might've been merged already
• You're looking at docs for the released version, main branch docs are usually ahead of released versions.
  • Docs for exact released version can be found at https://github.com/k0sproject/k0s/tree/<version>/docs

-->

Version

$ k0s version
v1.21.2+k0s.1

Platform Which platform did you run k0s on?

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.2 LTS
Release:	20.04
Codename:	focal

What happened? I am unable to standup a dual stack cluster

How To Reproduce

• Grab a default config k0s default-config > k0s.yaml
• Add the dual stack settings as per the docs page

apiVersion: k0s.k0sproject.io/v1beta1
kind: Cluster
metadata:
  name: k0s
spec:
  api:
    address: 168.119.88.161
    port: 6443
    k0sApiPort: 9443
    sans:
    - 168.119.88.161
    - 10.96.0.1
    - 10.96.0.10
    - 10.99.82.25
  storage:
    type: etcd
    etcd:
      peerAddress: 168.119.88.161
  network:
    podCIDR: 10.244.0.0/16
    serviceCIDR: 10.96.0.0/12
    provider: calico
    calico:
      mode: bird
    dualStack:
      enabled: true
      IPv6podCIDR: fd00::/108
      IPv6serviceCIDR: fd01::/108
    kuberouter:
      mtu: 0
      peerRouterIPs: ""
      peerRouterASNs: ""
      autoMTU: true
    kubeProxy:
      disabled: false
      mode: ipvs
  podSecurityPolicy:
    defaultPolicy: 00-k0s-privileged
  telemetry:
    enabled: true
  installConfig:
    users:
      etcdUser: etcd
      kineUser: kube-apiserver
      konnectivityUser: konnectivity-server
      kubeAPIserverUser: kube-apiserver
      kubeSchedulerUser: kube-scheduler
  images:
    konnectivity:
      image: us.gcr.io/k8s-artifacts-prod/kas-network-proxy/proxy-agent
      version: v0.0.21
    metricsserver:
      image: gcr.io/k8s-staging-metrics-server/metrics-server
      version: v0.3.7
    kubeproxy:
      image: k8s.gcr.io/kube-proxy
      version: v1.21.2
    coredns:
      image: docker.io/coredns/coredns
      version: 1.7.0
    calico:
      cni:
        image: docker.io/calico/cni
        version: v3.18.1
      node:
        image: docker.io/calico/node
        version: v3.18.1
      kubecontrollers:
        image: docker.io/calico/kube-controllers
        version: v3.18.1
    kuberouter:
      cni:
        image: docker.io/cloudnativelabs/kube-router
        version: v1.2.1
      cniInstaller:
        image: quay.io/k0sproject/cni-node
        version: 0.1.0
    default_pull_policy: IfNotPresent
  konnectivity:
    agentPort: 8132
    adminPort: 8133

• k0s install controller -c k0s.yaml --enable-worker
• k0s start

Expected behavior I expected pods not to crash

Screenshots & Logs

$ k0s kubectl logs -n kube-system calico-kube-controllers-6d8ccdbf46-plf6n
2021-07-26 03:00:40.084 [INFO][1] main.go 92: Loaded configuration from environment config=&config.Config{LogLevel:"info", WorkloadEndpointWorkers:1, ProfileWorkers:1, PolicyWorkers:1, NodeWorkers:1, Kubeconfig:"", DatastoreType:"kubernetes"}
W0726 03:00:40.085349       1 client_config.go:552] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
2021-07-26 03:00:40.085 [INFO][1] main.go 113: Ensuring Calico datastore is initialized
2021-07-26 03:00:50.085 [ERROR][1] client.go 261: Error getting cluster information config ClusterInformation="default" error=Get "https://10.96.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": context deadline exceeded
2021-07-26 03:00:50.086 [FATAL][1] main.go 118: Failed to initialize Calico datastore error=Get "https://10.96.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": context deadline exceeded

$ k0s kubectl get pods -A
NAMESPACE     NAME                                       READY   STATUS             RESTARTS   AGE
kube-system   calico-kube-controllers-6d8ccdbf46-plf6n   0/1     CrashLoopBackOff   8          20m
kube-system   calico-node-q9nhs                          1/1     Running            0          20m
kube-system   coredns-5ccbdcc4c4-4dv25                   0/1     Running            0          20m
kube-system   konnectivity-agent-s4572                   1/1     Running            0          20m
kube-system   kube-proxy-gg9fs                           1/1     Running            0          20m
kube-system   metrics-server-59d8698d9-qvn5g             0/1     Running            8          20m

Additional context None

Hi,

I updated the github actions to include OPT 24 and Elixir 1.12 - I realise that this has made it more complex but I didn't want to assume you were dropping any Elixir support with the OPT 24 / Elixir 1.12 releases.

Cheers Sam

Thanks

hey @knrz - i didn't spot a new release yet, is there anything blocking?

Bumps ex_doc from 0.24.1 to 0.24.2. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/elixir-lang/ex_doc/blob/master/CHANGELOG.md">ex_doc's changelog</a>.</em></p> <blockquote> <h2>v0.24.2 (2021-04-06)</h2> <ul> <li> <p>Enhancements</p> <ul> <li>Support stepped range syntax</li> </ul> </li> <li> <p>Bug fixes</p> <ul> <li>Add spaces on paragraph endings for search results</li> <li>Fix bug defining app name in config</li> <li>Fix rendering void elements (<code><br></code> etc)</li> </ul> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/elixir-lang/ex_doc/commit/241d739e84a13a380bb8d1b70f75fdb168946919"><code>241d739</code></a> Release v0.24.2</li> <li><a href="https://github.com/elixir-lang/ex_doc/commit/dcf303d0dd76c52038e29103cac74cc4101dbf9a"><code>dcf303d</code></a> Generating void elements correctly on <code>DocAST.to_string</code> (<a href="https://github-redirect.dependabot.com/elixir-lang/ex_doc/issues/1351">#1351</a>)</li> <li><a href="https://github.com/elixir-lang/ex_doc/commit/609d9765dd6f098dc298e5d6db6430859ee934ec"><code>609d976</code></a> Fix bug defining app name in config (<a href="https://github-redirect.dependabot.com/elixir-lang/ex_doc/issues/1347">#1347</a>)</li> <li><a href="https://github.com/elixir-lang/ex_doc/commit/fd4a0c7fd5a2a6c50e7822115d2ca0f4af533941"><code>fd4a0c7</code></a> Support stepped range syntax (<a href="https://github-redirect.dependabot.com/elixir-lang/ex_doc/issues/1346">#1346</a>)</li> <li><a href="https://github.com/elixir-lang/ex_doc/commit/fd55c41a95c209c5fc657683b7fcb5b12fb0be45"><code>fd55c41</code></a> Add spaces on paragraph endings for search results (<a href="https://github-redirect.dependabot.com/elixir-lang/ex_doc/issues/1167">#1167</a>)</li> <li>See full diff in <a href="https://github.com/elixir-lang/ex_doc/compare/v0.24.1...v0.24.2">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

Bumps timex from 3.7.3 to 3.7.5. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/bitwalker/timex/blob/master/CHANGELOG.md">timex's changelog</a>.</em></p> <blockquote> <h2>3.7.5</h2> <h3>Added/Changed</h3> <ul> <li>Added <code>Timex.Timezone.get/3</code> to allow requesting timezones using utc or wall clock as desired</li> </ul> <h3>Fixed</h3> <ul> <li>Addressed issues <a href="https://github-redirect.dependabot.com/bitwalker/timex/issues/652">#652</a>, <a href="https://github-redirect.dependabot.com/bitwalker/timex/issues/658">#658</a>, <a href="https://github-redirect.dependabot.com/bitwalker/timex/issues/659">#659</a>, <a href="https://github-redirect.dependabot.com/bitwalker/timex/issues/656">#656</a>, <a href="https://github-redirect.dependabot.com/bitwalker/timex/issues/654">#654</a>, <a href="https://github-redirect.dependabot.com/bitwalker/timex/issues/653">#653</a></li> </ul> <h2>3.7.4</h2> <h3>Fixed</h3> <ul> <li>Addressed issues <a href="https://github-redirect.dependabot.com/bitwalker/timex/issues/647">#647</a>, <a href="https://github-redirect.dependabot.com/bitwalker/timex/issues/648">#648</a>, <a href="https://github-redirect.dependabot.com/bitwalker/timex/issues/649">#649</a>, <a href="https://github-redirect.dependabot.com/bitwalker/timex/issues/650">#650</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/bitwalker/timex/commit/916673de69ca24dc2359b3df0807a28c2f52cf3f"><code>916673d</code></a> fix: address non-alphabetic characters in some month abbrev translations</li> <li><a href="https://github.com/bitwalker/timex/commit/a1ace29804e0bc94810e2eb48d7fa1e7d3b59426"><code>a1ace29</code></a> version 3.7.5</li> <li><a href="https://github.com/bitwalker/timex/commit/a67c58bc14860a32b998d94e64bc4dd95b20e317"><code>a67c58b</code></a> feat: add timezone.get/3</li> <li><a href="https://github.com/bitwalker/timex/commit/695eef8123d0b2084887d19dbd898fd2f99aa0d8"><code>695eef8</code></a> fix: empty timezone edge case in posix parser</li> <li><a href="https://github.com/bitwalker/timex/commit/6ae414bf0fc38d7934e444ae5b5b7486202bcd1e"><code>6ae414b</code></a> fix: address some unhandled parser edge cases for ISO8601</li> <li><a href="https://github.com/bitwalker/timex/commit/b40650a34b45ade5e5f83e18e3745e08fb064ccb"><code>b40650a</code></a> fix: support set/2 :microsecond option without precision</li> <li><a href="https://github.com/bitwalker/timex/commit/1f4104d51cef6cd285af669ac0ec588858ab89c9"><code>1f4104d</code></a> fix: avoid delegating to tzdata for non-existent timezones</li> <li><a href="https://github.com/bitwalker/timex/commit/58fec13943b4c16c978f39691b6cdb3b047cbe8b"><code>58fec13</code></a> fix: converting with empty time zone (<a href="https://github-redirect.dependabot.com/bitwalker/timex/issues/655">#655</a>)</li> <li><a href="https://github.com/bitwalker/timex/commit/b7d45edebce4d5c008500ffa3c37dde9a5d4d049"><code>b7d45ed</code></a> fix: parser could fail on timezones when parsed date is invalid</li> <li><a href="https://github.com/bitwalker/timex/commit/cf0352ba7969bd2786fe586032ecca57ced33d6b"><code>cf0352b</code></a> version 3.7.4</li> <li>Additional commits viewable in <a href="https://github.com/bitwalker/timex/compare/3.7.3...3.7.5">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>