NodeGroup is the Schema for the NodeGroups API. Manages an EKS Node Group
Type
CRD
Group
eks.aws.upbound.io
Version
v1beta1
apiVersion: eks.aws.upbound.io/v1beta1
kind: NodeGroup
NodeGroupSpec defines the desired state of NodeGroup
No description provided.
Reference to a Cluster to populate clusterName.
Policies for referencing.
Selector for a Cluster to populate clusterName.
Policies for selection.
List of instance types associated with the EKS Node Group. Defaults to ["t3.medium"].
Reference to a Role in iam to populate nodeRoleArn.
Policies for referencing.
Selector for a Role in iam to populate nodeRoleArn.
Policies for selection.
Configuration block with remote access settings. See remote_access below for details.
References to SecurityGroup in ec2 to populate sourceSecurityGroupIds.
Policies for referencing.
Selector for a list of SecurityGroup in ec2 to populate sourceSecurityGroupIds.
Policies for selection.
Set of EC2 Security Group IDs to allow SSH access (port 22) from on the worker nodes. If you specify ec2_ssh_key, but do not specify this configuration when you create an EKS Node Group, port 22 on the worker nodes is opened to the Internet (0.0.0.0/0).
Configuration block with scaling settings. See scaling_config below for details.
References to Subnet in ec2 to populate subnetIds.
Policies for referencing.
Selector for a list of Subnet in ec2 to populate subnetIds.
Policies for selection.
Identifiers of EC2 Subnets to associate with the EKS Node Group. Amazon EKS managed node groups can be launched in both public and private subnets. If you plan to deploy load balancers to a subnet, the private subnet must have tag kubernetes.io/role/internal-elb, the public subnet must have tag kubernetes.io/role/elb.
Configuration block with update settings. See update_config below for details.
Reference to a Cluster in eks to populate version.
Policies for referencing.
Selector for a Cluster in eks to populate version.
Policies for selection.
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.
List of instance types associated with the EKS Node Group. Defaults to ["t3.medium"].
Reference to a Role in iam to populate nodeRoleArn.
Policies for referencing.
Selector for a Role in iam to populate nodeRoleArn.
Policies for selection.
Configuration block with remote access settings. See remote_access below for details.
References to SecurityGroup in ec2 to populate sourceSecurityGroupIds.
Policies for referencing.
Selector for a list of SecurityGroup in ec2 to populate sourceSecurityGroupIds.
Policies for selection.
Set of EC2 Security Group IDs to allow SSH access (port 22) from on the worker nodes. If you specify ec2_ssh_key, but do not specify this configuration when you create an EKS Node Group, port 22 on the worker nodes is opened to the Internet (0.0.0.0/0).
Configuration block with scaling settings. See scaling_config below for details.
References to Subnet in ec2 to populate subnetIds.
Policies for referencing.
Selector for a list of Subnet in ec2 to populate subnetIds.
Policies for selection.
Identifiers of EC2 Subnets to associate with the EKS Node Group. Amazon EKS managed node groups can be launched in both public and private subnets. If you plan to deploy load balancers to a subnet, the private subnet must have tag kubernetes.io/role/internal-elb, the public subnet must have tag kubernetes.io/role/elb.
Configuration block with update settings. See update_config below for details.
Reference to a Cluster in eks to populate version.
Policies for referencing.
Selector for a Cluster in eks to populate version.
Policies for selection.
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.
NodeGroupStatus defines the observed state of NodeGroup.
No description provided.
List of instance types associated with the EKS Node Group. Defaults to ["t3.medium"].
Configuration block with remote access settings. See remote_access below for details.
Set of EC2 Security Group IDs to allow SSH access (port 22) from on the worker nodes. If you specify ec2_ssh_key, but do not specify this configuration when you create an EKS Node Group, port 22 on the worker nodes is opened to the Internet (0.0.0.0/0).
List of objects containing information about underlying resources.
List of objects containing information about AutoScaling Groups.
Configuration block with scaling settings. See scaling_config below for details.
Identifiers of EC2 Subnets to associate with the EKS Node Group. Amazon EKS managed node groups can be launched in both public and private subnets. If you plan to deploy load balancers to a subnet, the private subnet must have tag kubernetes.io/role/internal-elb, the public subnet must have tag kubernetes.io/role/elb.
Configuration block with update settings. See update_config below for details.
Conditions of the resource.
sample-eks-ng
apiVersion: eks.aws.upbound.io/v1beta1
kind: NodeGroup
metadata:
name: sample-eks-ng
spec:
forProvider:
clusterNameRef:
name: sample-eks-cluster
nodeRoleArnRef:
name: sample-node-role
region: us-west-1
scalingConfig:
- desiredSize: 1
maxSize: 1
minSize: 1
subnetIdRefs:
- name: sample-subnet1
- name: sample-subnet2
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.