ServiceAttachment is the Schema for the ServiceAttachments API. Represents a ServiceAttachment resource.
Type
CRD
Group
compute.gcp.upbound.io
Version
v1beta1
apiVersion: compute.gcp.upbound.io/v1beta1
kind: ServiceAttachment
ServiceAttachmentSpec defines the desired state of ServiceAttachment
No description provided.
An array of projects that are allowed to connect to this service attachment. Structure is documented below.
An array of projects that are not allowed to connect to this service attachment.
If specified, the domain name will be used during the integration between the PSC connected endpoints and the Cloud DNS. For example, this is a valid domain name: "p.mycompany.com.". Current max number of domain names supported is 1.
An array of subnets that is provided for NAT in this service attachment.
References to Subnetwork to populate natSubnets.
Policies for referencing.
Selector for a list of Subnetwork to populate natSubnets.
Policies for selection.
Reference to a ForwardingRule in compute to populate targetService.
Policies for referencing.
Selector for a ForwardingRule in compute to populate targetService.
Policies for selection.
THIS IS AN ALPHA FIELD. Do not use it in production. It is not honored unless the relevant Crossplane feature flag is enabled, and may be changed or removed without notice. 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.
An array of projects that are allowed to connect to this service attachment. Structure is documented below.
An array of projects that are not allowed to connect to this service attachment.
If specified, the domain name will be used during the integration between the PSC connected endpoints and the Cloud DNS. For example, this is a valid domain name: "p.mycompany.com.". Current max number of domain names supported is 1.
THIS IS AN ALPHA FIELD. Do not use it in production. It is not honored unless the relevant Crossplane feature flag is enabled, and may be changed or removed without notice. 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.
ProviderReference specifies the provider that will be used to create, observe, update, and delete this managed resource. Deprecated: Please use ProviderConfigReference, i.e. providerConfigRef
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.
ServiceAttachmentStatus defines the observed state of ServiceAttachment.
No description provided.
An array of projects that are allowed to connect to this service attachment. Structure is documented below.
An array of projects that are not allowed to connect to this service attachment.
If specified, the domain name will be used during the integration between the PSC connected endpoints and the Cloud DNS. For example, this is a valid domain name: "p.mycompany.com.". Current max number of domain names supported is 1.
An array of subnets that is provided for NAT in this service attachment.
Conditions of the resource.
service-attachment
apiVersion: compute.gcp.upbound.io/v1beta1
kind: ServiceAttachment
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/serviceattachment
upjet.upbound.io/manual-intervention: Must be authorized to administer the domain gcp.example.com
labels:
testing.upbound.io/example-name: service-attachment
name: service-attachment
spec:
forProvider:
connectionPreference: ACCEPT_AUTOMATIC
description: A service attachment
domainNames:
- gcp.example.com.
enableProxyProtocol: true
natSubnetsRefs:
- name: service-attachment
region: us-central1
targetServiceSelector:
matchLabels:
testing.upbound.io/example-name: service-attachment