Mehrdad
Mehrdad
Same problem here using kubespray to initiate k8s cluster v1.19.2 on ESXi, using cilium as CNI and NFS for persistent volume. I tried both Helm chart available at helm GitHub...
@twright-msft @LuisBosquez any help?
@MSC02 what is the storage provider on the cluster that works?
same issue here looking forward for updates
we had the same issue the problem is that the log indicates ```ignoring OCI manifest sha256:1b86e767c10ce0c0e0e64e183a0065d114adbd38b13638811229a19a2d23c598. Manifest platform: linux/arm64, requested: linux/arm64"``` and it does not tell that actually they are...
longer names also causes cilium to OOM https://github.com/cilium/cilium/issues/32399
would highly appreciate and looking forward for this PR to be merged
can we bump this one in order to be able to set internal ip for robot servers? @pat-s the map should be comma seperated ``` HCLOUD_INSTANCES_INTERNAL_IP_MAP: node-1=1.1.1.1, node-2=2.2.2.2 ``` the...
we have the same issue ( we also happen to have robot servers in our cluster), I went the exact same path but there is no luck to pass network...
@jtackaberry I have figured it out you should set this variable in your deployment and then you can pass the networkID without crash HCLOUD_NETWORK_ROUTES_ENABLED: false