NodePool is the Schema for the NodePools API. An Anthos node pool running on Azure.
Type
CRD
Group
containerazure.gcp.upbound.io
Version
v1beta1
apiVersion: containerazure.gcp.upbound.io/v1beta1
kind: NodePool
NodePoolSpec defines the desired state of NodePool
No description provided.
Autoscaler configuration for this node pool.
Reference to a Cluster to populate cluster.
Policies for referencing.
Selector for a Cluster to populate cluster.
Policies for selection.
The node configuration of the node pool.
Proxy configuration for outbound HTTP(S) traffic.
Optional. Configuration related to the root volume provisioned for each node pool machine. When unspecified, it defaults to a 32-GiB Azure Disk.
SSH configuration for how to access the node pool machines.
The Management configuration for this node pool.
The constraint on the maximum number of pods that can be run simultaneously on a node in the node pool.
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.
Autoscaler configuration for this node pool.
The node configuration of the node pool.
Proxy configuration for outbound HTTP(S) traffic.
Optional. Configuration related to the root volume provisioned for each node pool machine. When unspecified, it defaults to a 32-GiB Azure Disk.
SSH configuration for how to access the node pool machines.
The Management configuration for this node pool.
The constraint on the maximum number of pods that can be run simultaneously on a node in the node pool.
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.
NodePoolStatus defines the observed state of NodePool.
No description provided.
Autoscaler configuration for this node pool.
The node configuration of the node pool.
Proxy configuration for outbound HTTP(S) traffic.
Optional. Configuration related to the root volume provisioned for each node pool machine. When unspecified, it defaults to a 32-GiB Azure Disk.
SSH configuration for how to access the node pool machines.
The Management configuration for this node pool.
The constraint on the maximum number of pods that can be run simultaneously on a node in the node pool.
Conditions of the resource.
example-azure-nodepool
apiVersion: containerazure.gcp.upbound.io/v1beta1
kind: NodePool
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:
annotations:
annotation-one: value-one
autoscaling:
- maxNodeCount: 3
minNodeCount: 2
client: projects/my-project-number/locations/us-west1/azureClients/example-client-nodepool
config:
- proxyConfig:
- resourceGroupId: /subscriptions/12345678-1234-1234-1234-123456789111/resourceGroups/my--dev-cluster
secretId: https://my--dev-keyvault.vault.azure.net/secrets/my--dev-secret/0000000000000000000000000000000000
rootVolume:
- sizeGib: 32
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
tags:
owner: mmv2
vmSize: Standard_DS2_v2
location: us-west1
maxPodsConstraint:
- maxPodsPerNode: 110
project: my-project-name
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]}
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.