Alex
Alex
My plan also gets "Killed" with provider version 0.21.0
Similar to [rparmer](https://github.com/fluxcd/terraform-provider-flux/issues/333#issuecomment-1320102556) I use templating function to modify the customization yaml. The fact that Flux provided the yaml files makes it pretty flexible.
I will use Flux GitRepository/Kustomization then. There is a bit hesitation to use `kustomize.toolkit.fluxcd.io/v1` too often because I suppose it will break the chain of `kustomize.config.k8s.io/v1beta1` files. For example if...
@nabheet very curious. Could you share snippet from your code?
@enocom I am running Cloud SQL Proxy in GKE as a separate K8s Deployment and I want the pods to be accessible only from the current namespace. There is a...
Not, yet. Currently, Cloud SQL Proxy as single container in a deployment just to try things out. After my trials I will either put Cloud SQL Proxy behind pgbouncer, as...
Thanks, enocom. I will follow the the example with PgBouncer then[1]. [2] https://github.com/GoogleCloudPlatform/cloud-sql-proxy/tree/main/examples/k8s-service
Can confirm this issue still exists in later versions. 0.27 in my case.
Same issue.
Maybe it would make sense to check the binary size as part of regression testing?