There is a second issue with this deployment, which is that it's running Kubernetes 1.23 on latest/edge charms that do not support Kubernetes 1.23. I see that the k8s snap channel config is unspecified in the bundle or overlays, so it's using the default value from the charms, which is out-of-date[1][2].
We can fix that default on our end easy enough. I'll open a couple PRs.
There is a second issue with this deployment, which is that it's running Kubernetes 1.23 on latest/edge charms that do not support Kubernetes 1.23. I see that the k8s snap channel config is unspecified in the bundle or overlays, so it's using the default value from the charms, which is out-of-date[1][2].
We can fix that default on our end easy enough. I'll open a couple PRs.
[1]: https:/ /github. com/charmed- kubernetes/ charm-kubernete s-control- plane/blob/ 45e994db6052740 cc43de8f80c87cf 16c335fa09/ config. yaml#L108 /github. com/charmed- kubernetes/ charm-kubernete s-worker/ blob/8a3751d57d 8c3b715da587191 3cde5e1e9c54433 /config. yaml#L14
[2]: https:/