A NodePool is an example API type.
Type
CRD
Group
k8s.ionoscloud.crossplane.io
Version
v1alpha1
apiVersion: k8s.ionoscloud.crossplane.io/v1alpha1
kind: NodePool
A NodePoolSpec defines the desired state of a NodePool.
NodePoolParameters are the observable fields of a NodePool. Required fields in order to create a K8s NodePool: ClusterConfig, Name, DatacenterConfig, NodeCount, CoresCount, RAMSize, AvailabilityZone, StorageType, StorageSize.
property to be set when auto-scaling needs to be enabled for the NodePool. By default, auto-scaling is not enabled.
The K8s Cluster on which the NodePool will be created.
ClusterIDRef references to a Cluster to retrieve its ID.
Policies for referencing.
ClusterIDSelector selects reference to a Cluster to retrieve its ClusterID.
Policies for selection.
A Datacenter, to which the user has access.
DatacenterIDRef references to a Datacenter to retrieve its ID.
Policies for referencing.
DatacenterIDSelector selects reference to a Datacenter to retrieve its DatacenterID.
Policies for selection.
Array of additional private LANs attached to worker nodes.
The LAN of an existing private LAN at the related datacenter.
LanIDRef references to a Lan to retrieve its ID.
Policies for referencing.
LanIDSelector selects reference to a Lan to retrieve its LanID.
Policies for selection.
The maintenance window is used for updating the software on the NodePool's nodes and for upgrading the NodePool's K8s version. If no value is given, one is chosen dynamically, so there is no fixed default.
Optional array of reserved public IP addresses to be used by the nodes. IPs must be from same location as the Datacenter used for the NodePool. The array must contain one more IP than the maximum possible number of nodes (nodeCount+1 for fixed number of nodes or maxNodeCount+1 when auto-scaling is used). The extra IP is used when the nodes are rebuilt. IPs can be set directly or via reference and indexes.
Use IPs to set specific IPs to the resource. If both IPs and IPsBlockConfigs are set,
only ips field will be considered.
Use IpsBlockConfigs to reference existing IPBlocks, and to mention the indexes for the IPs. Indexes start from 0, and multiple indexes can be set. If no index is set, all IPs from the corresponding IPBlock will be assigned to the resource.
Indexes are referring to the IPs indexes retrieved from the IPBlock. Indexes are starting from 0. If no index is set, all IPs from the corresponding IPBlock will be assigned.
IPBlockIDRef references to a IPBlock to retrieve its ID.
Policies for referencing.
IPBlockIDSelector selects reference to a IPBlock to retrieve its IPBlockID.
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.
A NodePoolStatus represents the observed state of a NodePool.
NodePoolObservation are the observable fields of a NodePool.
No description provided.
No description provided.
Conditions of the resource.