A IPFailover is an example API type.
Type
CRD
Group
compute.ionoscloud.crossplane.io
Version
v1alpha1
apiVersion: compute.ionoscloud.crossplane.io/v1alpha1
kind: IPFailover
A IPFailoverSpec defines the desired state of a IPFailover.
IPFailoverParameters are the observable fields of a IPFailover. Required values when creating a IPFailover: DatacenterConfig, LanConfig (LAN resource must be a public LAN), NicConfig, IPConfig.
DatacenterConfig contains information about the datacenter resource on which the resource will be created.
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.
IPConfig must have a public IP for which the group is responsible for. IP can be set directly, using ipConfig.ip or via reference and index. If both ip and ipBlockConfig is set, only ip field will be considered. It is recommended to use ip field instead of ipBlockConfig field if the ipBlock contains multiple ips.
Use IpBlockConfig to reference existing IPBlock, and to mention the index for the IP. Index starts from 0 and it must be provided.
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.
LanConfig contains information about the lan resource on which the resource will be created.
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.
NicConfig contains information about the nic resource on which the resource will be created.
NicIDRef references to a Nic to retrieve its ID.
Policies for referencing.
NicIDSelector selects reference to a Nic to retrieve its NicID.
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 IPFailoverStatus represents the observed state of a IPFailover.
Conditions of the resource.
exampleipfailover
apiVersion: compute.ionoscloud.crossplane.io/v1alpha1
kind: IPFailover
metadata:
name: exampleipfailover
spec:
forProvider:
datacenterConfig:
datacenterIdRef:
name: example
ipConfig:
ipBlockConfig:
index: 0
ipBlockIdRef:
name: exampleipblock
lanConfig:
lanIdRef:
name: examplelan
nicConfig:
nicIdRef:
name: examplenic
managementPolicies:
- "*"
providerConfigRef:
name: example