NodePool is the Schema for the NodePools API. An Anthos node pool running on AWS.
Type
CRD
Group
containeraws.gcp.upbound.io
Version
v1beta1
apiVersion: containeraws.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 configuration of the node pool.
The ARN of the AWS KMS key used to encrypt node pool configuration.
Proxy configuration for outbound HTTP(S) traffic.
Optional. Template for the root volume provisioned for node pool nodes. Volumes will be provisioned in the availability zone assigned to the node pool subnet. When unspecified, it defaults to 32 GiB with the GP2 volume type.
Optional. The IDs of additional security groups to add to nodes in this pool. The manager will automatically create security groups with minimum rules needed for a functioning cluster.
Optional. The SSH configuration.
The constraint on the maximum number of pods that can be run simultaneously on a node in the node pool.
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.
NodePoolStatus defines the observed state of NodePool.
No description provided.
Conditions of the resource.
example-aws-nodepool
apiVersion: containeraws.gcp.upbound.io/v1beta1
kind: NodePool
metadata:
annotations:
meta.upbound.io/example-id: containeraws/v1beta1/nodepool
upjet.upbound.io/manual-intervention: AWS Infrastructure is required to test
this resource. Manifests for deploying these via provider-aws are
available in the `provider-aws` folder.
labels:
testing.upbound.io/example-name: example-aws-nodepool
name: example-aws-nodepool
spec:
forProvider:
annotations:
example-name: example-aws-nodepool
autoscaling:
- maxNodeCount: 5
minNodeCount: 1
clusterSelector:
matchLabels:
testing.upbound.io/example-name: example-aws-nodepool
config:
- configEncryption:
- kmsKeyArn: arn:aws:kms:my-aws-region:012345678910:key/12345678-1234-1234-1234-123456789111
iamInstanceProfile: containeraws-gcp-upbound-ctp-profile
instanceType: t3.medium
labels:
label-one: value-one
rootVolume:
- iops: 3000
kmsKeyArn: arn:aws:kms:my-aws-region:012345678910:key/12345678-1234-1234-1234-123456789111
sizeGib: 10
volumeType: GP3
tags:
tag-one: value-one
location: us-west1
maxPodsConstraint:
- maxPodsPerNode: 110
project: my-project-name
subnetId: subnet-00000000000000000
version: 1.23.8-gke.1700
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.