There is an error with the dev-image, as it cannot be startet on a Kubernetes cluster. Oneself and the pipeline can build it but I cannot get it running on any cluster.
In contrast, if I deploy an older dev-image (e.g. 0.2.2-dev-b61b7d043377756d563903ec628cadfb) and hotswap a local build into the cluster, it works just fine. Thus, I think there might be a problem with updated dependencies in the Makefile or similar.
For now, I deleted the malfunctioning dev-images from the registries and we can use the functioning old build (as nothing changed in the source code).
Steps to reproduce
Build the dev-image of Karydia (e.g. via the pipeline)
Deploy on a cluster
Try to access the Karydia pods (they are failing (e.g. liveness-probe fails))
Expected behavior
When I built the dev-image without any problems I would expect the pods to run normally on the cluster.
Description
There is an error with the dev-image, as it cannot be startet on a Kubernetes cluster. Oneself and the pipeline can build it but I cannot get it running on any cluster.
In contrast, if I deploy an older dev-image (e.g. 0.2.2-dev-b61b7d043377756d563903ec628cadfb) and hotswap a local build into the cluster, it works just fine. Thus, I think there might be a problem with updated dependencies in the Makefile or similar.
For now, I deleted the malfunctioning dev-images from the registries and we can use the functioning old build (as nothing changed in the source code).
Steps to reproduce
Expected behavior
When I built the dev-image without any problems I would expect the pods to run normally on the cluster.
Logs / console output / screenshots / affected lines of code