bakayolo
bakayolo
Definitely waiting for this feature!
Confirmed. I am getting the same issue with my helm chart https://github.com/kintoproj/kinto-helm Right now, the only workaround I found is to pass it as a `--set` parameter. Pretty annoying.
Having the same issue but with `kubect_file_documents` ``` data "kubectl_file_documents" "manifests" { content = file("${path.module}/manifests/metrics_server.yaml") } resource "kubectl_manifest" "metrics_server" { count = length(data.kubectl_file_documents.manifests.documents) yaml_body = element(data.kubectl_file_documents.manifests.documents, count.index) } ``` Resulting...
Same here, we're using Istio as well, and the rollout does not respect `maxSurge` and `maxUnavailable`.
Same here. Trying to improve the build of https://beta.kintohub.com/ by transitioning from DiD to Kanico but DiD is faster, even with caching. Seems that most of the time is indeed...
Hey @Utwo Thanks for trying. Can u try to run `kubectl get pod -n kintohub` while the deployment is running, then `kubectl logs -n kintohub [pod with error status] to...
You need to trigger a deployment first. Because the workflow pods have a TTL.
It is not possible. You must trigger a new deployment (delete this service) and immediately run the commands above. The pods used for the deployment workflow last Max 5 minutes...
@Utwo yeah it's because kubernetes now use containerd as a container engine. So everything works as expected?
@Utwo it's ur configuration ;) Did you see that -> https://github.com/kintoproj/kinto-helm/blob/main/charts/kinto/values.yaml#L103-L104 ?