Cluster is the Schema for the Clusters API. An Anthos cluster running on Azure.
Type
CRD
Group
containerazure.gcp.upbound.io
Version
v1beta1
apiVersion: containerazure.gcp.upbound.io/v1beta1
kind: Cluster
ClusterSpec defines the desired state of Cluster
No description provided.
Configuration related to the cluster RBAC settings.
Users that can perform operations as a cluster admin. A new ClusterRoleBinding will be created to grant the cluster-admin ClusterRole to the users. Up to ten admin users can be provided. For more info on RBAC, see https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles
Azure authentication configuration for management of Azure resources
Configuration related to the cluster control plane.
Optional. Configuration related to application-layer secrets encryption.
Optional. Configuration related to the main volume provisioned for each control plane replica. The main volume is in charge of storing all of the cluster's etcd state. When unspecified, it defaults to a 8-GiB Azure Disk.
Proxy configuration for outbound HTTP(S) traffic.
Configuration for where to place the control plane replicas. Up to three replica placement instances can be specified. If replica_placements is set, the replica placement instances will be applied to the three control plane replicas as evenly as possible.
Optional. Configuration related to the root volume provisioned for each control plane replica. When unspecified, it defaults to 32-GiB Azure Disk.
SSH configuration for how to access the underlying control plane machines.
Cluster-wide networking configuration.
The IP address range of the pods in this cluster, in CIDR notation (e.g. 10.96.0.0/14). All pods in the cluster get assigned a unique RFC1918 IPv4 address from these ranges. Only a single range is supported. This field cannot be changed after creation.
The IP address range for services in this cluster, in CIDR notation (e.g. 10.96.0.0/14). All services in the cluster get assigned a unique RFC1918 IPv4 address from these ranges. Only a single range is supported. This field cannot be changed after creating a cluster.
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.
ClusterStatus defines the observed state of Cluster.
No description provided.
Fleet configuration.
Output only. Workload Identity settings.
Conditions of the resource.
example-azure-cluster
apiVersion: containerazure.gcp.upbound.io/v1beta1
kind: Cluster
metadata:
annotations:
meta.upbound.io/example-id: containerazure/v1beta1/cluster
upjet.upbound.io/manual-intervention: "Azure Infrastructure is required to test
this resource. Manifests and scripts for deploying these via
provider-azure and the azure cli are available in the `provider-azure`
folder. Before creating this resource, run: -
`provider-azure/00-containerazure-application.sh` - `kubectl apply -f
provider-azure/00-containerazure-network.yaml` - `kubectl apply -f
provider-azure/01-containerazure-roles.yaml`"
labels:
testing.upbound.io/example-name: example-azure-cluster
name: example-azure-cluster
spec:
forProvider:
authorization:
- adminUsers:
- username: mmv2@google.com
azureRegion: westus2
client: projects/my-project-number/locations/us-west1/azureClients/example-azure-cluster
controlPlane:
- sshConfig:
- authorizedKey: ssh-rsa
AAAAB3NzaC1yc2EAAAADAQABAAACAQC8yaayO6lnb2v+SedxUMa2c8vtIEzCzBjM3EJJsv8Vm9zUDWR7dXWKoNGARUb2mNGXASvI6mFIDXTIlkQ0poDEPpMaXR0g2cb5xT8jAAJq7fqXL3+0rcJhY/uigQ+MrT6s+ub0BFVbsmGHNrMQttXX9gtmwkeAEvj3mra9e5pkNf90qlKnZz6U0SVArxVsLx07vHPHDIYrl0OPG4zUREF52igbBPiNrHJFDQJT/4YlDMJmo/QT/A1D6n9ocemvZSzhRx15/Arjowhr+VVKSbaxzPtEfY0oIg2SrqJnnr/l3Du5qIefwh5VmCZe4xopPUaDDoOIEFriZ88sB+3zz8ib8sk8zJJQCgeP78tQvXCgS+4e5W3TUg9mxjB6KjXTyHIVhDZqhqde0OI3Fy1UuVzRUwnBaLjBnAwP5EoFQGRmDYk/rEYe7HTmovLeEBUDQocBQKT4Ripm/xJkkWY7B07K/tfo56dGUCkvyIVXKBInCh+dLK7gZapnd4UWkY0xBYcwo1geMLRq58iFTLA2j/JmpmHXp7m0l7jJii7d44uD3tTIFYThn7NlOnvhLim/YcBK07GMGIN7XwrrKZKmxXaspw6KBWVhzuw1UPxctxshYEaMLfFg/bwOw8HvMPr9VtrElpSB7oiOh91PDIPdPBgHCi7N2QgQ5l/ZDBHieSpNrQ==
thomasrodgers
subnetId: /subscriptions/12345678-1234-1234-1234-123456789111/resourceGroups/my--dev-byo/providers/Microsoft.Network/virtualNetworks/my--dev-vnet/subnets/default
version: ${data.google_container_azure_versions.versions.valid_versions[0]}
fleet:
- project: my-project-number
location: us-west1
networking:
- podAddressCidrBlocks:
- 10.200.0.0/16
serviceAddressCidrBlocks:
- 10.32.0.0/24
virtualNetworkId: /subscriptions/12345678-1234-1234-1234-123456789111/resourceGroups/my--dev-byo/providers/Microsoft.Network/virtualNetworks/my--dev-vnet
project: my-project-name
resourceGroupId: /subscriptions/12345678-1234-1234-1234-123456789111/resourceGroups/my--dev-cluster
example-azure-nodepool
apiVersion: containerazure.gcp.upbound.io/v1beta1
kind: Cluster
metadata:
annotations:
meta.upbound.io/example-id: containerazure/v1beta1/nodepool
upjet.upbound.io/manual-intervention: "Azure Infrastructure is required to test
this resource. Manifests and scripts for deploying these via
provider-azure and the azure cli are available in the `provider-azure`
folder. Before creating this resource, run: -
`provider-azure/00-containerazure-application.sh` - `kubectl apply -f
provider-azure/00-containerazure-network.yaml` - `kubectl apply -f
provider-azure/01-containerazure-roles.yaml`"
labels:
testing.upbound.io/example-name: example-azure-nodepool
name: example-azure-nodepool
spec:
forProvider:
authorization:
- adminUsers:
- username: mmv2@google.com
azureRegion: westus2
clientSelector:
matchLabels:
testing.upbound.io/example-name: example-azure-nodepool
controlPlane:
- sshConfig:
- authorizedKey: ssh-rsa
AAAAB3NzaC1yc2EAAAADAQABAAACAQC8yaayO6lnb2v+SedxUMa2c8vtIEzCzBjM3EJJsv8Vm9zUDWR7dXWKoNGARUb2mNGXASvI6mFIDXTIlkQ0poDEPpMaXR0g2cb5xT8jAAJq7fqXL3+0rcJhY/uigQ+MrT6s+ub0BFVbsmGHNrMQttXX9gtmwkeAEvj3mra9e5pkNf90qlKnZz6U0SVArxVsLx07vHPHDIYrl0OPG4zUREF52igbBPiNrHJFDQJT/4YlDMJmo/QT/A1D6n9ocemvZSzhRx15/Arjowhr+VVKSbaxzPtEfY0oIg2SrqJnnr/l3Du5qIefwh5VmCZe4xopPUaDDoOIEFriZ88sB+3zz8ib8sk8zJJQCgeP78tQvXCgS+4e5W3TUg9mxjB6KjXTyHIVhDZqhqde0OI3Fy1UuVzRUwnBaLjBnAwP5EoFQGRmDYk/rEYe7HTmovLeEBUDQocBQKT4Ripm/xJkkWY7B07K/tfo56dGUCkvyIVXKBInCh+dLK7gZapnd4UWkY0xBYcwo1geMLRq58iFTLA2j/JmpmHXp7m0l7jJii7d44uD3tTIFYThn7NlOnvhLim/YcBK07GMGIN7XwrrKZKmxXaspw6KBWVhzuw1UPxctxshYEaMLfFg/bwOw8HvMPr9VtrElpSB7oiOh91PDIPdPBgHCi7N2QgQ5l/ZDBHieSpNrQ==
thomasrodgers
subnetId: /subscriptions/12345678-1234-1234-1234-123456789111/resourceGroups/my--dev-byo/providers/Microsoft.Network/virtualNetworks/my--dev-vnet/subnets/default
version: ${data.google_container_azure_versions.versions.valid_versions[0]}
fleet:
- project: my-project-number
location: us-west1
networking:
- podAddressCidrBlocks:
- 10.200.0.0/16
serviceAddressCidrBlocks:
- 10.32.0.0/24
virtualNetworkId: /subscriptions/12345678-1234-1234-1234-123456789111/resourceGroups/my--dev-byo/providers/Microsoft.Network/virtualNetworks/my--dev-vnet
project: my-project-name
resourceGroupId: /subscriptions/12345678-1234-1234-1234-123456789111/resourceGroups/my--dev-cluster
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.