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

basic example of spinning up an alloydb instance #268

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

drewwells
Copy link
Contributor

@drewwells drewwells commented Jul 31, 2024

the process involves two steps because we don't know the
service attachment url at declaration time

after serviceattachemnt url is available, provision a composition
that will setup forwarding rules to the google vpc and a hostname
to resolve the psc hostname

@drewwells drewwells force-pushed the alloydbExample branch 6 times, most recently from da71d00 to 0eae025 Compare August 23, 2024 17:26
@drewwells
Copy link
Contributor Author

DEMO

k describe xnetworkingrecord
...
Spec:
  Composition Ref:
    Name:  alloydb-psc-test
  Composition Revision Ref:
    Name:                     alloydb-psc-test-f2a98d9
  Composition Update Policy:  Automatic
  Parameters:
    Network:                  projects/gcp-eng-ddiaas-dev/global/networks/ddiaas-dev-use1-vpc
    Psc Dns Name:             30f6af49-74c7-4058-9b00-8a29cff777c9.3f031303-8e9c-4941-8b77-1aafad235014.us-east1.alloydb-psc.goog.
    Region:                   us-east1
    Service Attachment Link:  https://www.googleapis.com/compute/v1/projects/e25a3c1c1c0b768f3p-tp/regions/us-east1/serviceAttachments/alloydb-30f6af49-74c-alloydb-psc-test-sa
    Subnetwork:               projects/gcp-eng-ddiaas-dev/regions/us-east1/subnetworks/private-service-connect
  Resource Refs:
    API Version:  dns.gcp.upbound.io/v1beta2
    Kind:         ManagedZone
    Name:         alloydb-psc-network-w92qk
    API Version:  compute.gcp.upbound.io/v1beta1
    Kind:         Address
    Name:         alloydb-psc-network-bpmkm
    API Version:  dns.gcp.upbound.io/v1beta1
    Kind:         RecordSet
    Name:         alloydb-psc-network-9vv4w
    API Version:  compute.gcp.upbound.io/v1beta1
    Kind:         ForwardingRule
    Name:         alloydb-psc-network-dc2t2
Status:
  Address:    100.127.252.4
  Addressid:  projects/gcp-eng-ddiaas-dev/regions/us-east1/addresses/alloydb-psc-network-bpmkm
  Conditions:
    Last Transition Time:  2024-08-23T13:20:12Z
    Reason:                ReconcileSuccess
    Status:                True
    Type:                  Synced
    Last Transition Time:  2024-08-23T17:22:42Z
    Reason:                Available
    Status:                True
    Type:                  Ready
  Managedzone Ref:         alloydb-psc-network-w92qk
Events:
  Type    Reason             Age                    From                                                             Message
  ----    ------             ----                   ----                                                             -------
  Normal  SelectComposition  36m                    defined/compositeresourcedefinition.apiextensions.crossplane.io  Selected composition revision: alloydb-psc-test-bb56e10
  Normal  SelectComposition  32m                    defined/compositeresourcedefinition.apiextensions.crossplane.io  Selected composition revision: alloydb-psc-test-62a4bee
  Normal  ComposeResources   103s (x517 over 4h7m)  defined/compositeresourcedefinition.apiextensions.crossplane.io  Successfully composed resources

@drewwells drewwells force-pushed the alloydbExample branch 2 times, most recently from 85a7c4b to bfeace1 Compare August 24, 2024 23:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant