Cluster is the Schema for the Clusters API. Allows management of Yandex Kubernetes Cluster. For more information, see
Type
CRD
Group
kubernetes.yandex-cloud.upjet.crossplane.io
Version
v1alpha1
apiVersion: kubernetes.yandex-cloud.upjet.crossplane.io/v1alpha1
kind: Cluster
ClusterSpec defines the desired state of Cluster
No description provided.
Reference to a Folder in resourcemanager to populate folderId.
Policies for referencing.
Selector for a Folder in resourcemanager to populate folderId.
Policies for selection.
cluster KMS provider parameters.
Reference to a SymmetricKey in kms to populate keyId.
Policies for referencing.
Selector for a SymmetricKey in kms to populate keyId.
Policies for selection.
Kubernetes master configuration options. The structure is documented below.
(Computed) Maintenance policy for Kubernetes master. If policy is omitted, automatic revision upgrades of the kubernetes master 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.
(Computed) This structure specifies maintenance window, when update for master is allowed. When omitted, it defaults to any time. To specify time of day interval, for all days, one element should be provided, with two fields set, start_time and duration. Please see zonal_cluster_resource_name config example.
Cluster master's instances locations array (zone and subnet). Cannot be used together with zonal or regional. Currently, supports either one, for zonal master, or three instances of master_location. Can be updated inplace. When creating regional cluster (three master instances), its region will be evaluated automatically by backend. 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.
Master Logging options. The structure is documented below.
Initialize parameters for Regional Master (highly available master). The structure is documented below.
Array of locations, where master instances will be allocated. 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.
List of security group IDs to which the Kubernetes cluster belongs.
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.
Initialize parameters for Zonal Master (single node master). 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.
Reference to a Network in vpc to populate networkId.
Policies for referencing.
Selector for a Network in vpc to populate networkId.
Policies for selection.
Network Implementation options. The structure is documented below.
Cilium network implementation configuration. No options exist.
Reference to a SecurityGroup in vpc to populate nodeServiceAccountId.
Policies for referencing.
Selector for a SecurityGroup in vpc to populate nodeServiceAccountId.
Policies for selection.
Reference to a SecurityGroup in vpc to populate serviceAccountId.
Policies for referencing.
Selector for a SecurityGroup in vpc to populate serviceAccountId.
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.
Reference to a Folder in resourcemanager to populate folderId.
Policies for referencing.
Selector for a Folder in resourcemanager to populate folderId.
Policies for selection.
cluster KMS provider parameters.
Reference to a SymmetricKey in kms to populate keyId.
Policies for referencing.
Selector for a SymmetricKey in kms to populate keyId.
Policies for selection.
Kubernetes master configuration options. The structure is documented below.
(Computed) Maintenance policy for Kubernetes master. If policy is omitted, automatic revision upgrades of the kubernetes master 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.
(Computed) This structure specifies maintenance window, when update for master is allowed. When omitted, it defaults to any time. To specify time of day interval, for all days, one element should be provided, with two fields set, start_time and duration. Please see zonal_cluster_resource_name config example.
Cluster master's instances locations array (zone and subnet). Cannot be used together with zonal or regional. Currently, supports either one, for zonal master, or three instances of master_location. Can be updated inplace. When creating regional cluster (three master instances), its region will be evaluated automatically by backend. 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.
Master Logging options. The structure is documented below.
Initialize parameters for Regional Master (highly available master). The structure is documented below.
Array of locations, where master instances will be allocated. 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.
List of security group IDs to which the Kubernetes cluster belongs.
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.
Initialize parameters for Zonal Master (single node master). 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.
Reference to a Network in vpc to populate networkId.
Policies for referencing.
Selector for a Network in vpc to populate networkId.
Policies for selection.
Network Implementation options. The structure is documented below.
Cilium network implementation configuration. No options exist.
Reference to a SecurityGroup in vpc to populate nodeServiceAccountId.
Policies for referencing.
Selector for a SecurityGroup in vpc to populate nodeServiceAccountId.
Policies for selection.
Reference to a SecurityGroup in vpc to populate serviceAccountId.
Policies for referencing.
Selector for a SecurityGroup in vpc to populate serviceAccountId.
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.
ClusterStatus defines the observed state of Cluster.
No description provided.
cluster KMS provider parameters.
Kubernetes master configuration options. The structure is documented below.
(Computed) Maintenance policy for Kubernetes master. If policy is omitted, automatic revision upgrades of the kubernetes master 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.
(Computed) This structure specifies maintenance window, when update for master is allowed. When omitted, it defaults to any time. To specify time of day interval, for all days, one element should be provided, with two fields set, start_time and duration. Please see zonal_cluster_resource_name config example.
Cluster master's instances locations array (zone and subnet). Cannot be used together with zonal or regional. Currently, supports either one, for zonal master, or three instances of master_location. Can be updated inplace. When creating regional cluster (three master instances), its region will be evaluated automatically by backend. The structure is documented below.
Master Logging options. The structure is documented below.
List of security group IDs to which the Kubernetes cluster belongs.
(Computed) Information about cluster version. The structure is documented below.
Network Implementation options. The structure is documented below.
Cilium network implementation configuration. No options exist.
Conditions of the resource.
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.