Tom Wieczorek
Tom Wieczorek
Related: #4121
/cc #1919 haven't tested it in a while, but now that Alpine 3.20 has RISC-V support, you should be able to compile k0s directly on the VisionFive using Docker. It'll...
That was my last attempt: https://github.com/k0sproject/k0s/issues/1919#issuecomment-1746962060 You can have a look at the diff to figure out what to tweak.
@ncopa concerning https://github.com/k0sproject/k0s/issues/1919#issuecomment-1761203870, do you think we can simply unconditionally switch from `binutils-gold` to `binutils`?
@IngwiePhoenix Checking back in after a long time 😁 You might give k0s 1.33 a spin. It should "just compile" now on RISC-V, and all the core images have a...
Are you connecting via DNS names or IP addresses? Can you maybe post the output of `ssh -vvv ...` from before and after, to see what might be the problem?...
Currently, an `EtcdMember` custom resource looks like the following: ```yaml apiVersion: etcd.k0sproject.io/v1beta1 kind: EtcdMember memberID: 21e943ed8772de19 metadata: creationTimestamp: "2024-05-03T11:32:11Z" generation: 1 name: etcdmember-controller-2 resourceVersion: "362" uid: 641f2594-881a-4e8f-939e-94535d6b5904 peerAddress: 172.27.200.93 status:...
Right. I think this was an oversight when creating the `Chart` struct. The `Timeout` field uses `time.Duration` instead of `k8s.io/apimachinery/pkg/apis/meta/v1.Duration`. > Changing that setting to 10000000 results in a valid...
> I'd say that using nanoseconds in this context is less than optimal :) Using minutes should cover all reasonable use-cases. Agree. As said, this was definitely not on purpose....
Concerning > Normally, I would have said that this should probably be fixed in a backwards-compatible way, but I doubt that anyone will get this right (having to specify it...