Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CloudSQL Private IP instance support (ServiceNetworkingConnection) #55

Closed
nrobert13 opened this issue Oct 21, 2019 · 5 comments
Closed
Labels
enhancement New feature or request

Comments

@nrobert13
Copy link

would be nice to be able to customize the Instance, like:

  • connectivity type ( Private/ Public IP)
  • associated networking ( Private IP )
  • authorized networks ( Public IP )
@AlexBulankou
Copy link
Contributor

@nrobert13 , thanks for reporting ti! It will be possible once Config Connector supports ServiceNetworkingConnection resource, similar to Terraform's google_service_networking_connection . Then you should be able to configure private IP instance, similar how you can do with TF.
Will that address your scenario?
Is not being able to configure private IP instance currently blocking for you?

@AlexBulankou AlexBulankou changed the title CloudSQL instance connectivity CloudSQL Private IP instance support (ServiceNetworkingConnection) Oct 31, 2019
@AlexBulankou AlexBulankou added the enhancement New feature or request label Oct 31, 2019
@nrobert13
Copy link
Author

Hi Alex,

we were able to create an SQL instance with both the Public/Private IP connectivity and configure associated networks, the only thing missing is the authorized networks.
Used this manifest:

---
apiVersion: sql.cnrm.cloud.google.com/v1alpha3
kind: SQLInstance
metadata:
  name: inst2912
  namespace: test
spec:
  databaseVersion: POSTGRES_9_6
  region: europe-west1
  settings:
    tier: db-f1-micro
    ipConfiguration:
      privateNetwork: "projects/test/global/networks/cluster-2-test-network"
      ipv4Enabled: true

not sure though if this is planned/expected behavior of the controller or just accidental, as the only thing what we specify is the privateNetwork and still the Public IP is getting configured on the resource.

@kibbles-n-bytes
Copy link
Contributor

Thanks nrobert13; we are currently working on support for ServiceNetworkingConnection, which will set up the private SQL instance peering. We will follow up with a change to SQLInstance to convert the spec.settings.ipConfiguration.privateNetwork field into a resource reference in order to match the other reference patterns.

@AlexBulankou
Copy link
Contributor

@nrobert13 , ServiceNetworkingConnection is now supported (examples ) - does it work for your requirements?

@kibbles-n-bytes
Copy link
Contributor

Closing this issue out now that ServiceNetworkingConnection is supported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants