cloud-sql-proxy-operator
cloud-sql-proxy-operator copied to clipboard
A Kubernetes Operator to automatically configure secure connections to Cloud SQL
Currently the operator only supports built-in kubernetes workload types. We would like input from the community about which additional kinds of workloads you would like the operator to support. Please...
## Background Official support for sidecar containers will be released as alpha in K8s 1.28. [KEP-753](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/753-sidecar-containers/README.md) KEP-753 solves a number of pod lifecycle problems that plague the current sidecar container...
Any thoughts about / plans for creating a Helm Chart? As is, it is a bit of a lift to convert the 30-odd resources in https://storage.googleapis.com/cloud-sql-connectors/cloud-sql-proxy-operator/v0.5.0/cloud-sql-proxy-operator.yaml into something that can...
Ensure that the CI environments for e2e tests are only valid for 1 week. Then they are deleted and recreated fresh. This will help ensure that the environments remain stable....
Implement an E2E test that uses GKE workload identity to authenticate with the database.
Implement a locking mechanism on the E2E test environment for PRs, so that only one E2E test may run at the same time. E2E test jobs will wait and poll...
Currently we use LDFLAGS to embed the contents of version.txt and the head SHA from our git repo into the built artifact. Instead we want to use go embed. Investigate...
Roll up the status for the individual containers and report it in status.conditions for the AuthProxyWorkload resource.
This is a work-in-progress draft of the helm chart for the operator. Here are the configurable values implemented so far: - [x] Operator Version (default latest. This controls the default...