ShardingInstance is the Schema for the ShardingInstances API. Provide a resource to create a Mongodb sharding instance.
Type
CRD
Group
mongodb.tencentcloud.crossplane.io
Version
v1alpha1
apiVersion: mongodb.tencentcloud.crossplane.io/v1alpha1
kind: ShardingInstance
ShardingInstanceSpec defines the desired state of ShardingInstance
No description provided.
A list of nodes deployed in multiple availability zones. For more information, please use the API DescribeSpecInfo.
- Multi-availability zone deployment nodes can only be deployed in 3 different availability zones. It is not supported to deploy most nodes of the cluster in the same availability zone. For example, a 3-node cluster does not support the deployment of 2 nodes in the same zone.
- Version 4.2 and above are not supported.
- Read-only disaster recovery instances are not supported.
- Basic network cannot be selected. A list of nodes deployed in multiple availability zones. For more information, please use the API DescribeSpecInfo.
- Multi-availability zone deployment nodes can only be deployed in 3 different availability zones. It is not supported to deploy most nodes of the cluster in the same availability zone. For example, a 3-node cluster does not support the deployment of 2 nodes in the same zone.
- Version 4.2 and above are not supported.
- Read-only disaster recovery instances are not supported.
- Basic network cannot be selected.
ID of the security group. ID of the security group.
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 VPC in vpc to populate vpcId.
Policies for referencing.
Selector for a VPC in vpc to populate vpcId.
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.
A list of nodes deployed in multiple availability zones. For more information, please use the API DescribeSpecInfo.
- Multi-availability zone deployment nodes can only be deployed in 3 different availability zones. It is not supported to deploy most nodes of the cluster in the same availability zone. For example, a 3-node cluster does not support the deployment of 2 nodes in the same zone.
- Version 4.2 and above are not supported.
- Read-only disaster recovery instances are not supported.
- Basic network cannot be selected. A list of nodes deployed in multiple availability zones. For more information, please use the API DescribeSpecInfo.
- Multi-availability zone deployment nodes can only be deployed in 3 different availability zones. It is not supported to deploy most nodes of the cluster in the same availability zone. For example, a 3-node cluster does not support the deployment of 2 nodes in the same zone.
- Version 4.2 and above are not supported.
- Read-only disaster recovery instances are not supported.
- Basic network cannot be selected.
ID of the security group. ID of the security group.
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 VPC in vpc to populate vpcId.
Policies for referencing.
Selector for a VPC in vpc to populate vpcId.
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.
ShardingInstanceStatus defines the observed state of ShardingInstance.
No description provided.
A list of nodes deployed in multiple availability zones. For more information, please use the API DescribeSpecInfo.
- Multi-availability zone deployment nodes can only be deployed in 3 different availability zones. It is not supported to deploy most nodes of the cluster in the same availability zone. For example, a 3-node cluster does not support the deployment of 2 nodes in the same zone.
- Version 4.2 and above are not supported.
- Read-only disaster recovery instances are not supported.
- Basic network cannot be selected. A list of nodes deployed in multiple availability zones. For more information, please use the API DescribeSpecInfo.
- Multi-availability zone deployment nodes can only be deployed in 3 different availability zones. It is not supported to deploy most nodes of the cluster in the same availability zone. For example, a 3-node cluster does not support the deployment of 2 nodes in the same zone.
- Version 4.2 and above are not supported.
- Read-only disaster recovery instances are not supported.
- Basic network cannot be selected.
ID of the security group. ID of the security group.
Conditions of the resource.
© 2024 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.