Open wainersm opened 1 week ago
One thing that I didn't understand is why it provisioned a cluster with:
kataCI-kata-deploy-nightly-56423cbbfe66-dragonball-ubuntu-amd64-s-o
and not
kataCI-kata-deploy-nightly-56423cbbfe66-qemu-runtime-rs-ubuntu-amd64-s-o
Because both characters count exceed 63:
$ echo -n kataCI-kata-deploy-nightly-56423cbbfe66-dragonball-ubuntu-amd64-s-o | wc -m
67
$ echo -n kataCI-kata-deploy-nightly-56423cbbfe66-qemu-runtime-rs-ubuntu-amd64-s-o | wc -m
72
Now, if one assume that special characters aren't counted (e.g. dash) then both are below the 63 chars limit:
$ echo -n kataCI-kata-deploy-nightly-56423cbbfe66-dragonball-ubuntu-amd64-s-o | tr -d '-' | wc -m
58
$ echo -n kataCI-kata-deploy-nightly-56423cbbfe66-qemu-runtime-rs-ubuntu-amd64-s-o | tr -d '-' | wc -m
61
Interestingly I can create a cluster with kataCIkatadeploynightly56423cbbfe66qemuruntimersubuntuamd64so
(removed the dashes )
Nightly
kata-containers-ci-on-push / run-kata-deploy-tests-on-aks / run-kata-deploy-tests (ubuntu, qemu-runtime-rs)
has always failed because the cluster name is too big, exceeding the limit of chars of AKS...