NodeGroup is the Schema for the NodeGroups API. Allows management of Yandex Kubernetes Node Group. For more information, see
Type
CRD
Group
kubernetes.yandex-cloud.upjet.crossplane.io
Version
v1alpha1
apiVersion: kubernetes.yandex-cloud.upjet.crossplane.io/v1alpha1
kind: NodeGroup
NodeGroupSpec defines the desired state of NodeGroup
No description provided.
This argument specify subnets (zones), that will be used by node group compute instances. The structure is documented below.
Repeated field, that specify subnets (zones), that will be used by node group compute instances. The structure is documented below.
Reference to a Subnet in vpc to populate subnetId.
Policies for referencing.
Selector for a Subnet in vpc to populate subnetId.
Policies for selection.
A list of allowed unsafe sysctl parameters for this node group. For more details see documentation.
Reference to a Cluster to populate clusterId.
Policies for referencing.
Selector for a Cluster to populate clusterId.
Policies for selection.
Deploy policy of the node group. The structure is documented below.
Template used to create compute instances in this Kubernetes node group. The structure is documented below.
Container network configuration. The structure is documented below.
Container runtime configuration. The structure is documented below.
GPU settings. The structure is documented below.
An array with the network interfaces that will be attached to the instance. The structure is documented below.
Security group ids for network interface.
References to SecurityGroup in vpc to populate securityGroupIds.
Policies for referencing.
Selector for a list of SecurityGroup in vpc to populate securityGroupIds.
Policies for selection.
The IDs of the subnets.
References to Subnet in vpc to populate subnetIds.
Policies for referencing.
Selector for a list of Subnet in vpc to populate subnetIds.
Policies for selection.
The placement policy configuration. The structure is documented below.
No description provided.
The scheduling policy for the instances in node group. The structure is documented below.
(Computed) Maintenance policy for this Kubernetes node group. If policy is omitted, automatic revision upgrades are enabled and could happen at any time. Revision upgrades are performed only within the same minor version, e.g. 1.13. Minor version upgrades (e.g. 1.13->1.14) should be performed manually. The structure is documented below.
A list of Kubernetes taints, that are applied to all the nodes of this Kubernetes node group.
Scale policy of the node group. The structure is documented below.
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 argument specify subnets (zones), that will be used by node group compute instances. The structure is documented below.
Repeated field, that specify subnets (zones), that will be used by node group compute instances. The structure is documented below.
Reference to a Subnet in vpc to populate subnetId.
Policies for referencing.
Selector for a Subnet in vpc to populate subnetId.
Policies for selection.
A list of allowed unsafe sysctl parameters for this node group. For more details see documentation.
Reference to a Cluster to populate clusterId.
Policies for referencing.
Selector for a Cluster to populate clusterId.
Policies for selection.
Deploy policy of the node group. The structure is documented below.
Template used to create compute instances in this Kubernetes node group. The structure is documented below.
Container network configuration. The structure is documented below.
Container runtime configuration. The structure is documented below.
GPU settings. The structure is documented below.
An array with the network interfaces that will be attached to the instance. The structure is documented below.
Security group ids for network interface.
References to SecurityGroup in vpc to populate securityGroupIds.
Policies for referencing.
Selector for a list of SecurityGroup in vpc to populate securityGroupIds.
Policies for selection.
The IDs of the subnets.
References to Subnet in vpc to populate subnetIds.
Policies for referencing.
Selector for a list of Subnet in vpc to populate subnetIds.
Policies for selection.
The placement policy configuration. The structure is documented below.
No description provided.
The scheduling policy for the instances in node group. The structure is documented below.
(Computed) Maintenance policy for this Kubernetes node group. If policy is omitted, automatic revision upgrades are enabled and could happen at any time. Revision upgrades are performed only within the same minor version, e.g. 1.13. Minor version upgrades (e.g. 1.13->1.14) should be performed manually. The structure is documented below.
A list of Kubernetes taints, that are applied to all the nodes of this Kubernetes node group.
Scale policy of the node group. The structure is documented below.
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.
This argument specify subnets (zones), that will be used by node group compute instances. The structure is documented below.
A list of allowed unsafe sysctl parameters for this node group. For more details see documentation.
Deploy policy of the node group. The structure is documented below.
Template used to create compute instances in this Kubernetes node group. The structure is documented below.
Container network configuration. The structure is documented below.
Container runtime configuration. The structure is documented below.
GPU settings. The structure is documented below.
An array with the network interfaces that will be attached to the instance. The structure is documented below.
Security group ids for network interface.
The IDs of the subnets.
The placement policy configuration. The structure is documented below.
No description provided.
The scheduling policy for the instances in node group. The structure is documented below.
(Computed) Maintenance policy for this Kubernetes node group. If policy is omitted, automatic revision upgrades are enabled and could happen at any time. Revision upgrades are performed only within the same minor version, e.g. 1.13. Minor version upgrades (e.g. 1.13->1.14) should be performed manually. The structure is documented below.
A list of Kubernetes taints, that are applied to all the nodes of this Kubernetes node group.
Scale policy of the node group. The structure is documented below.
(Computed) Information about Kubernetes node group version. The structure is documented below.
Conditions of the resource.
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.