Client is the Schema for the Clients API. AzureClient resources hold client authentication information needed by the Anthos Multi-Cloud API to manage Azure resources on your Azure subscription.When an AzureCluster is created, an AzureClient resource needs to be provided and all operations on Azure resources associated to that cluster will authenticate to Azure services using the given client.AzureClient resources are immutable and cannot be modified upon creation.Each AzureClient resource is bound to a single Azure Active Directory Application and tenant.
Type
CRD
Group
containerazure.gcp.upbound.io
Version
v1beta1
apiVersion: containerazure.gcp.upbound.io/v1beta1
kind: Client
ClientSpec defines the desired state of Client
No description provided.
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.
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.
ClientStatus defines the observed state of Client.
No description provided.
Conditions of the resource.
example-azure-nodepool
apiVersion: containerazure.gcp.upbound.io/v1beta1
kind: Client
metadata:
annotations:
meta.upbound.io/example-id: containerazure/v1beta1/nodepool
upjet.upbound.io/manual-intervention: "Before creating this client, run:
`provider-azure/00-containerazure-application.sh` After creating this
client, run: `provider-azure/authorize_client.sh ${client name}`"
labels:
testing.upbound.io/example-name: example-azure-nodepool
name: example-azure-nodepool
spec:
forProvider:
applicationId: 12345678-1234-1234-1234-123456789111
location: us-west1
project: my-project-name
tenantId: 12345678-1234-1234-1234-123456789111
example-azure-client
apiVersion: containerazure.gcp.upbound.io/v1beta1
kind: Client
metadata:
annotations:
meta.upbound.io/example-id: containerazure/v1beta1/client
upjet.upbound.io/manual-intervention: "Before creating this client, run:
`provider-azure/00-containerazure-application.sh`"
labels:
testing.upbound.io/example-name: example-azure-client
name: example-azure-client
spec:
forProvider:
applicationId: 12345678-1234-1234-1234-123456789111
location: us-west1
project: my-project-name
tenantId: 12345678-1234-1234-1234-123456789111
example-azure-cluster
apiVersion: containerazure.gcp.upbound.io/v1beta1
kind: Client
metadata:
annotations:
meta.upbound.io/example-id: containerazure/v1beta1/cluster
upjet.upbound.io/manual-intervention: "Before creating this client, run:
`provider-azure/00-containerazure-application.sh` After creating this
client, run: `provider-azure/authorize_client.sh ${client name}`"
labels:
testing.upbound.io/example-name: example-azure-cluster
name: example-azure-cluster
spec:
forProvider:
applicationId: 12345678-1234-1234-1234-123456789111
location: us-west1
project: my-project-name
tenantId: 12345678-1234-1234-1234-123456789111
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.