etcd 3.5 support for ARM64

[lacrimal]

Hi,
Few days ago created new k0s installation and spotted this communicate on my arm64 instances:
enabling ETCD_UNSUPPORTED_ARCH=arm64 override - you may encounter problems with etcd
Apologize my question if it is to childish - etcd v3.5 shows here that ARM64 is fully supported.
Do k0s use other version of etcd ?

[Skaronator]

At least the code already knows that arm64 and amd64 are supported:

k0s/pkg/component/controller/etcd.go

Lines 313 to 318 in 333b906

	// https://github.com/etcd-io/etcd/blob/v3.5.2/server/etcdmain/etcd.go#L467-L472
	if runtime.GOARCH != "amd64" && runtime.GOARCH != "arm64" {
	if os.Getenv("ETCD_UNSUPPORTED_ARCH") != runtime.GOARCH {
	return fmt.Errorf("running ETCD on %s requires ETCD_UNSUPPORTED_ARCH=%s ", runtime.GOARCH, runtime.GOARCH)
	}
	}

Looking at the commit history, they are also using 3.5.8+ 4deb733

[lacrimal]

As I see this code will display warning about unsupported architecture on arm64 while it is supported on etcd v3.5+

[jnummelin]

@lacrimal which k0s version are you seeing this on?

Like @Skaronator mentioned, the code should detect arm64 properly as supported arch so I wonder where this message comes from 🤔

[lacrimal]

Ok, let's go by details I can provide maybe problem is here.
Installation is made on Oracle Cloud Ampere A1 based VM, version of k0s is v1.27.4+k0s.0, - there are cpu details:

#>uname -a
5.15.0-6.80.3.1.el9uek.aarch64 #2 SMP Tue Jan 10 11:35:24 PST 2023 aarch64 aarch64 aarch64 GNU/Linux
#>lscpu
Architecture:           aarch64
  CPU op-mode(s):       32-bit, 64-bit
  Byte Order:           Little Endian
CPU(s):                 2
  On-line CPU(s) list:  0,1
Vendor ID:              ARM
  BIOS Vendor ID:       QEMU
  Model name:           Neoverse-N1
    BIOS Model name:    virt-4.2
    Model:              1
    Thread(s) per core: 1
    Core(s) per socket: 2
    Socket(s):          1
    Stepping:           r3p1
    BogoMIPS:           50.00
    Flags:              fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
NUMA:
  NUMA node(s):         1
  NUMA node0 CPU(s):    0,1
Vulnerabilities:
  Itlb multihit:        Not affected
  L1tf:                 Not affected
  Mds:                  Not affected
  Meltdown:             Not affected
  Mmio stale data:      Not affected
  Retbleed:             Mitigation; CSV2, BHB
  Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1:           Mitigation; __user pointer sanitization
  Spectre v2:           Mitigation; CSV2, BHB
  Srbds:                Not affected
  Tsx async abort:      Not affected

[jnummelin]

ah, are you using k0sctl to deploy the cluster? If so, it seems k0sctl has this obsolete warning still in the code base.

https://github.com/k0sproject/k0sctl/blob/main/phase/arm_prepare.go#L47

[lacrimal]

ah, are you using k0sctl to deploy the cluster? If so, it seems k0sctl has this obsolete warning still in the code base.

https://github.com/k0sproject/k0sctl/blob/main/phase/arm_prepare.go#L47

sorry - thought that it is obvious that I'm using k0sctl - so nothing to worry - warning is harmless and obsolete

Thanks for explanation

[jnummelin]

fix to remove the warning in k0sctl is on the way: k0sproject/k0sctl#519

Hence, I'll close this up on k0s repo.