Instance is the Schema for the Instances API. Creates a Google Bigtable instance.
Type
CRD
Group
bigtable.gcp.upbound.io
Version
v1beta1
apiVersion: bigtable.gcp.upbound.io/v1beta1
kind: Instance
InstanceSpec defines the desired state of Instance
No description provided.
A block of cluster configuration options. This can be specified at least once, and up to as many as possible within 8 cloud regions. Removing the field entirely from the config will cause the provider to default to the backend value. See structure below.
Autoscaling config for the cluster, contains the following arguments:
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
A block of cluster configuration options. This can be specified at least once, and up to as many as possible within 8 cloud regions. Removing the field entirely from the config will cause the provider to default to the backend value. See structure below.
Autoscaling config for the cluster, contains the following arguments:
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
InstanceStatus defines the observed state of Instance.
No description provided.
A block of cluster configuration options. This can be specified at least once, and up to as many as possible within 8 cloud regions. Removing the field entirely from the config will cause the provider to default to the backend value. See structure below.
Autoscaling config for the cluster, contains the following arguments:
Conditions of the resource.
instance
apiVersion: bigtable.gcp.upbound.io/v1beta1
kind: Instance
metadata:
annotations:
meta.upbound.io/example-id: bigtable/v1beta1/table
labels:
testing.upbound.io/example-name: instance
name: instance
spec:
forProvider:
cluster:
- clusterId: tf-instance-cluster
numNodes: 3
storageType: HDD
zone: us-central1-b
deletionProtection: false
instance
apiVersion: bigtable.gcp.upbound.io/v1beta1
kind: Instance
metadata:
annotations:
meta.upbound.io/example-id: bigtable/v1beta1/appprofile
labels:
testing.upbound.io/example-name: instance
name: instance
spec:
forProvider:
cluster:
- clusterId: cluster-1
numNodes: 3
storageType: HDD
zone: us-central1-a
- clusterId: cluster-2
numNodes: 3
storageType: HDD
zone: us-central1-b
- clusterId: cluster-3
numNodes: 3
storageType: HDD
zone: us-central1-c
deletionProtection: false
production-instance
apiVersion: bigtable.gcp.upbound.io/v1beta1
kind: Instance
metadata:
annotations:
meta.upbound.io/example-id: bigtable/v1beta1/instanceiampolicy
labels:
testing.upbound.io/example-name: production-instance
name: production-instance
spec:
forProvider:
cluster:
- clusterId: tf-instance-cluster
numNodes: 1
storageType: HDD
zone: us-central1-b
deletionProtection: false
labels:
my-label: prod-label
instance
apiVersion: bigtable.gcp.upbound.io/v1beta1
kind: Instance
metadata:
annotations:
meta.upbound.io/example-id: bigtable/v1beta1/tableiammember
labels:
testing.upbound.io/example-name: instance
name: instance
spec:
forProvider:
cluster:
- clusterId: tf-instance-cluster
numNodes: 3
storageType: HDD
zone: us-central1-b
deletionProtection: false
instance
apiVersion: bigtable.gcp.upbound.io/v1beta1
kind: Instance
metadata:
annotations:
meta.upbound.io/example-id: bigtable/v1beta1/tableiambinding
labels:
testing.upbound.io/example-name: instance
name: instance
spec:
forProvider:
cluster:
- clusterId: tf-instance-cluster
numNodes: 3
storageType: HDD
zone: us-central1-b
deletionProtection: false
instance
apiVersion: bigtable.gcp.upbound.io/v1beta1
kind: Instance
metadata:
annotations:
meta.upbound.io/example-id: bigtable/v1beta1/tableiampolicy
labels:
testing.upbound.io/example-name: instance
name: instance
spec:
forProvider:
cluster:
- clusterId: tf-instance-cluster
numNodes: 3
storageType: HDD
zone: us-central1-b
deletionProtection: false
production-instance
apiVersion: bigtable.gcp.upbound.io/v1beta1
kind: Instance
metadata:
annotations:
meta.upbound.io/example-id: bigtable/v1beta1/instanceiambinding
labels:
testing.upbound.io/example-name: production-instance
name: production-instance
spec:
forProvider:
cluster:
- clusterId: tf-instance-cluster
numNodes: 1
storageType: HDD
zone: us-central1-b
deletionProtection: false
labels:
my-label: prod-label
production-instance
apiVersion: bigtable.gcp.upbound.io/v1beta1
kind: Instance
metadata:
annotations:
meta.upbound.io/example-id: bigtable/v1beta1/instanceiammember
labels:
testing.upbound.io/example-name: production-instance
name: production-instance
spec:
forProvider:
cluster:
- clusterId: tf-instance-cluster
numNodes: 1
storageType: HDD
zone: us-central1-b
deletionProtection: false
labels:
my-label: prod-label
production-instance
apiVersion: bigtable.gcp.upbound.io/v1beta1
kind: Instance
metadata:
annotations:
meta.upbound.io/example-id: bigtable/v1beta1/instance
labels:
testing.upbound.io/example-name: production-instance
name: production-instance
spec:
forProvider:
cluster:
- clusterId: tf-instance-cluster
numNodes: 1
storageType: HDD
zone: us-central1-b
deletionProtection: false
labels:
my-label: prod-label
instance
apiVersion: bigtable.gcp.upbound.io/v1beta1
kind: Instance
metadata:
annotations:
meta.upbound.io/example-id: bigtable/v1beta1/garbagecollectionpolicy
labels:
testing.upbound.io/example-name: instance
name: instance
spec:
forProvider:
cluster:
- clusterId: tf-instance-cluster
numNodes: 3
storageType: HDD
zone: us-central1-b
deletionProtection: false
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.