Chapter 15. Infrastructure [config.openshift.io/v1]
- Description
-
Infrastructure holds cluster-wide information about Infrastructure. The canonical name is
cluster
Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer). - Type
-
object
- Required
-
spec
-
15.1. Specification
Property | Type | Description |
---|---|---|
|
| APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources |
|
| Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds |
| Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata | |
|
| spec holds user settable values for configuration |
|
| status holds observed values from the cluster. They may not be overridden. |
15.1.1. .spec
- Description
- spec holds user settable values for configuration
- Type
-
object
Property | Type | Description |
---|---|---|
|
|
cloudConfig is a reference to a ConfigMap containing the cloud provider configuration file. This configuration file is used to configure the Kubernetes cloud provider integration when using the built-in cloud provider integration or the external cloud controller manager. The namespace for this config map is openshift-config. cloudConfig should only be consumed by the kube_cloud_config controller. The controller is responsible for using the user configuration in the spec for various platforms and combining that with the user provided ConfigMap in this field to create a stitched kube cloud config. The controller generates a ConfigMap |
|
| platformSpec holds desired information specific to the underlying infrastructure provider. |
15.1.2. .spec.cloudConfig
- Description
-
cloudConfig is a reference to a ConfigMap containing the cloud provider configuration file. This configuration file is used to configure the Kubernetes cloud provider integration when using the built-in cloud provider integration or the external cloud controller manager. The namespace for this config map is openshift-config. cloudConfig should only be consumed by the kube_cloud_config controller. The controller is responsible for using the user configuration in the spec for various platforms and combining that with the user provided ConfigMap in this field to create a stitched kube cloud config. The controller generates a ConfigMap
kube-cloud-config
inopenshift-config-managed
namespace with the kube cloud config is stored incloud.conf
key. All the clients are expected to use the generated ConfigMap only. - Type
-
object
Property | Type | Description |
---|---|---|
|
| Key allows pointing to a specific key/value inside of the configmap. This is useful for logical file references. |
|
|
15.1.3. .spec.platformSpec
- Description
- platformSpec holds desired information specific to the underlying infrastructure provider.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| AlibabaCloud contains settings specific to the Alibaba Cloud infrastructure provider. |
|
| AWS contains settings specific to the Amazon Web Services infrastructure provider. |
|
| Azure contains settings specific to the Azure infrastructure provider. |
|
| BareMetal contains settings specific to the BareMetal platform. |
|
| EquinixMetal contains settings specific to the Equinix Metal infrastructure provider. |
|
| ExternalPlatformType represents generic infrastructure provider. Platform-specific components should be supplemented separately. |
|
| GCP contains settings specific to the Google Cloud Platform infrastructure provider. |
|
| IBMCloud contains settings specific to the IBMCloud infrastructure provider. |
|
| Kubevirt contains settings specific to the kubevirt infrastructure provider. |
|
| Nutanix contains settings specific to the Nutanix infrastructure provider. |
|
| OpenStack contains settings specific to the OpenStack infrastructure provider. |
|
| Ovirt contains settings specific to the oVirt infrastructure provider. |
|
| PowerVS contains settings specific to the IBM Power Systems Virtual Servers infrastructure provider. |
|
| type is the underlying infrastructure provider for the cluster. This value controls whether infrastructure automation such as service load balancers, dynamic volume provisioning, machine creation and deletion, and other integrations are enabled. If None, no infrastructure automation is enabled. Allowed values are "AWS", "Azure", "BareMetal", "GCP", "Libvirt", "OpenStack", "VSphere", "oVirt", "KubeVirt", "EquinixMetal", "PowerVS", "AlibabaCloud", "Nutanix" and "None". Individual components may not support all platforms, and must handle unrecognized platforms as None if they do not support that platform. |
|
| VSphere contains settings specific to the VSphere infrastructure provider. |
15.1.4. .spec.platformSpec.alibabaCloud
- Description
- AlibabaCloud contains settings specific to the Alibaba Cloud infrastructure provider.
- Type
-
object
15.1.5. .spec.platformSpec.aws
- Description
- AWS contains settings specific to the Amazon Web Services infrastructure provider.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| serviceEndpoints list contains custom endpoints which will override default service endpoint of AWS Services. There must be only one ServiceEndpoint for a service. |
|
| AWSServiceEndpoint store the configuration of a custom url to override existing defaults of AWS Services. |
15.1.6. .spec.platformSpec.aws.serviceEndpoints
- Description
- serviceEndpoints list contains custom endpoints which will override default service endpoint of AWS Services. There must be only one ServiceEndpoint for a service.
- Type
-
array
15.1.7. .spec.platformSpec.aws.serviceEndpoints[]
- Description
- AWSServiceEndpoint store the configuration of a custom url to override existing defaults of AWS Services.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| name is the name of the AWS service. The list of all the service names can be found at https://docs.aws.amazon.com/general/latest/gr/aws-service-information.html This must be provided and cannot be empty. |
|
| url is fully qualified URI with scheme https, that overrides the default generated endpoint for a client. This must be provided and cannot be empty. |
15.1.8. .spec.platformSpec.azure
- Description
- Azure contains settings specific to the Azure infrastructure provider.
- Type
-
object
15.1.9. .spec.platformSpec.baremetal
- Description
- BareMetal contains settings specific to the BareMetal platform.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| apiServerInternalIPs are the IP addresses to contact the Kubernetes API server that can be used by components inside the cluster, like kubelets using the infrastructure rather than Kubernetes networking. These are the IPs for a self-hosted load balancer in front of the API servers. In dual stack clusters this list contains two IP addresses, one from IPv4 family and one from IPv6. In single stack clusters a single IP address is expected. When omitted, values from the status.apiServerInternalIPs will be used. Once set, the list cannot be completely removed (but its second entry can). |
|
| ingressIPs are the external IPs which route to the default ingress controller. The IPs are suitable targets of a wildcard DNS record used to resolve default route host names. In dual stack clusters this list contains two IP addresses, one from IPv4 family and one from IPv6. In single stack clusters a single IP address is expected. When omitted, values from the status.ingressIPs will be used. Once set, the list cannot be completely removed (but its second entry can). |
|
| machineNetworks are IP networks used to connect all the OpenShift cluster nodes. Each network is provided in the CIDR format and should be IPv4 or IPv6, for example "10.0.0.0/8" or "fd00::/8". |
15.1.10. .spec.platformSpec.equinixMetal
- Description
- EquinixMetal contains settings specific to the Equinix Metal infrastructure provider.
- Type
-
object
15.1.11. .spec.platformSpec.external
- Description
- ExternalPlatformType represents generic infrastructure provider. Platform-specific components should be supplemented separately.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| PlatformName holds the arbitrary string representing the infrastructure provider name, expected to be set at the installation time. This field is solely for informational and reporting purposes and is not expected to be used for decision-making. |
15.1.12. .spec.platformSpec.gcp
- Description
- GCP contains settings specific to the Google Cloud Platform infrastructure provider.
- Type
-
object
15.1.13. .spec.platformSpec.ibmcloud
- Description
- IBMCloud contains settings specific to the IBMCloud infrastructure provider.
- Type
-
object
15.1.14. .spec.platformSpec.kubevirt
- Description
- Kubevirt contains settings specific to the kubevirt infrastructure provider.
- Type
-
object
15.1.15. .spec.platformSpec.nutanix
- Description
- Nutanix contains settings specific to the Nutanix infrastructure provider.
- Type
-
object
- Required
-
prismCentral
-
prismElements
-
Property | Type | Description |
---|---|---|
|
| failureDomains configures failure domains information for the Nutanix platform. When set, the failure domains defined here may be used to spread Machines across prism element clusters to improve fault tolerance of the cluster. |
|
| NutanixFailureDomain configures failure domain information for the Nutanix platform. |
|
| prismCentral holds the endpoint address and port to access the Nutanix Prism Central. When a cluster-wide proxy is installed, by default, this endpoint will be accessed via the proxy. Should you wish for communication with this endpoint not to be proxied, please add the endpoint to the proxy spec.noProxy list. |
|
| prismElements holds one or more endpoint address and port data to access the Nutanix Prism Elements (clusters) of the Nutanix Prism Central. Currently we only support one Prism Element (cluster) for an OpenShift cluster, where all the Nutanix resources (VMs, subnets, volumes, etc.) used in the OpenShift cluster are located. In the future, we may support Nutanix resources (VMs, etc.) spread over multiple Prism Elements (clusters) of the Prism Central. |
|
| NutanixPrismElementEndpoint holds the name and endpoint data for a Prism Element (cluster) |
15.1.16. .spec.platformSpec.nutanix.failureDomains
- Description
- failureDomains configures failure domains information for the Nutanix platform. When set, the failure domains defined here may be used to spread Machines across prism element clusters to improve fault tolerance of the cluster.
- Type
-
array
15.1.17. .spec.platformSpec.nutanix.failureDomains[]
- Description
- NutanixFailureDomain configures failure domain information for the Nutanix platform.
- Type
-
object
- Required
-
cluster
-
name
-
subnets
-
Property | Type | Description |
---|---|---|
|
| cluster is to identify the cluster (the Prism Element under management of the Prism Central), in which the Machine’s VM will be created. The cluster identifier (uuid or name) can be obtained from the Prism Central console or using the prism_central API. |
|
| name defines the unique name of a failure domain. Name is required and must be at most 64 characters in length. It must consist of only lower case alphanumeric characters and hyphens (-). It must start and end with an alphanumeric character. This value is arbitrary and is used to identify the failure domain within the platform. |
|
| subnets holds a list of identifiers (one or more) of the cluster’s network subnets for the Machine’s VM to connect to. The subnet identifiers (uuid or name) can be obtained from the Prism Central console or using the prism_central API. |
|
| NutanixResourceIdentifier holds the identity of a Nutanix PC resource (cluster, image, subnet, etc.) |
15.1.18. .spec.platformSpec.nutanix.failureDomains[].cluster
- Description
- cluster is to identify the cluster (the Prism Element under management of the Prism Central), in which the Machine’s VM will be created. The cluster identifier (uuid or name) can be obtained from the Prism Central console or using the prism_central API.
- Type
-
object
- Required
-
type
-
Property | Type | Description |
---|---|---|
|
| name is the resource name in the PC. It cannot be empty if the type is Name. |
|
| type is the identifier type to use for this resource. |
|
| uuid is the UUID of the resource in the PC. It cannot be empty if the type is UUID. |
15.1.19. .spec.platformSpec.nutanix.failureDomains[].subnets
- Description
- subnets holds a list of identifiers (one or more) of the cluster’s network subnets for the Machine’s VM to connect to. The subnet identifiers (uuid or name) can be obtained from the Prism Central console or using the prism_central API.
- Type
-
array
15.1.20. .spec.platformSpec.nutanix.failureDomains[].subnets[]
- Description
- NutanixResourceIdentifier holds the identity of a Nutanix PC resource (cluster, image, subnet, etc.)
- Type
-
object
- Required
-
type
-
Property | Type | Description |
---|---|---|
|
| name is the resource name in the PC. It cannot be empty if the type is Name. |
|
| type is the identifier type to use for this resource. |
|
| uuid is the UUID of the resource in the PC. It cannot be empty if the type is UUID. |
15.1.21. .spec.platformSpec.nutanix.prismCentral
- Description
- prismCentral holds the endpoint address and port to access the Nutanix Prism Central. When a cluster-wide proxy is installed, by default, this endpoint will be accessed via the proxy. Should you wish for communication with this endpoint not to be proxied, please add the endpoint to the proxy spec.noProxy list.
- Type
-
object
- Required
-
address
-
port
-
Property | Type | Description |
---|---|---|
|
| address is the endpoint address (DNS name or IP address) of the Nutanix Prism Central or Element (cluster) |
|
| port is the port number to access the Nutanix Prism Central or Element (cluster) |
15.1.22. .spec.platformSpec.nutanix.prismElements
- Description
- prismElements holds one or more endpoint address and port data to access the Nutanix Prism Elements (clusters) of the Nutanix Prism Central. Currently we only support one Prism Element (cluster) for an OpenShift cluster, where all the Nutanix resources (VMs, subnets, volumes, etc.) used in the OpenShift cluster are located. In the future, we may support Nutanix resources (VMs, etc.) spread over multiple Prism Elements (clusters) of the Prism Central.
- Type
-
array
15.1.23. .spec.platformSpec.nutanix.prismElements[]
- Description
- NutanixPrismElementEndpoint holds the name and endpoint data for a Prism Element (cluster)
- Type
-
object
- Required
-
endpoint
-
name
-
Property | Type | Description |
---|---|---|
|
| endpoint holds the endpoint address and port data of the Prism Element (cluster). When a cluster-wide proxy is installed, by default, this endpoint will be accessed via the proxy. Should you wish for communication with this endpoint not to be proxied, please add the endpoint to the proxy spec.noProxy list. |
|
| name is the name of the Prism Element (cluster). This value will correspond with the cluster field configured on other resources (eg Machines, PVCs, etc). |
15.1.24. .spec.platformSpec.nutanix.prismElements[].endpoint
- Description
- endpoint holds the endpoint address and port data of the Prism Element (cluster). When a cluster-wide proxy is installed, by default, this endpoint will be accessed via the proxy. Should you wish for communication with this endpoint not to be proxied, please add the endpoint to the proxy spec.noProxy list.
- Type
-
object
- Required
-
address
-
port
-
Property | Type | Description |
---|---|---|
|
| address is the endpoint address (DNS name or IP address) of the Nutanix Prism Central or Element (cluster) |
|
| port is the port number to access the Nutanix Prism Central or Element (cluster) |
15.1.25. .spec.platformSpec.openstack
- Description
- OpenStack contains settings specific to the OpenStack infrastructure provider.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| apiServerInternalIPs are the IP addresses to contact the Kubernetes API server that can be used by components inside the cluster, like kubelets using the infrastructure rather than Kubernetes networking. These are the IPs for a self-hosted load balancer in front of the API servers. In dual stack clusters this list contains two IP addresses, one from IPv4 family and one from IPv6. In single stack clusters a single IP address is expected. When omitted, values from the status.apiServerInternalIPs will be used. Once set, the list cannot be completely removed (but its second entry can). |
|
| ingressIPs are the external IPs which route to the default ingress controller. The IPs are suitable targets of a wildcard DNS record used to resolve default route host names. In dual stack clusters this list contains two IP addresses, one from IPv4 family and one from IPv6. In single stack clusters a single IP address is expected. When omitted, values from the status.ingressIPs will be used. Once set, the list cannot be completely removed (but its second entry can). |
|
| machineNetworks are IP networks used to connect all the OpenShift cluster nodes. Each network is provided in the CIDR format and should be IPv4 or IPv6, for example "10.0.0.0/8" or "fd00::/8". |
15.1.26. .spec.platformSpec.ovirt
- Description
- Ovirt contains settings specific to the oVirt infrastructure provider.
- Type
-
object
15.1.27. .spec.platformSpec.powervs
- Description
- PowerVS contains settings specific to the IBM Power Systems Virtual Servers infrastructure provider.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| serviceEndpoints is a list of custom endpoints which will override the default service endpoints of a Power VS service. |
|
| PowervsServiceEndpoint stores the configuration of a custom url to override existing defaults of PowerVS Services. |
15.1.28. .spec.platformSpec.powervs.serviceEndpoints
- Description
- serviceEndpoints is a list of custom endpoints which will override the default service endpoints of a Power VS service.
- Type
-
array
15.1.29. .spec.platformSpec.powervs.serviceEndpoints[]
- Description
- PowervsServiceEndpoint stores the configuration of a custom url to override existing defaults of PowerVS Services.
- Type
-
object
- Required
-
name
-
url
-
Property | Type | Description |
---|---|---|
|
| name is the name of the Power VS service. Few of the services are IAM - https://cloud.ibm.com/apidocs/iam-identity-token-api ResourceController - https://cloud.ibm.com/apidocs/resource-controller/resource-controller Power Cloud - https://cloud.ibm.com/apidocs/power-cloud |
|
| url is fully qualified URI with scheme https, that overrides the default generated endpoint for a client. This must be provided and cannot be empty. |
15.1.30. .spec.platformSpec.vsphere
- Description
- VSphere contains settings specific to the VSphere infrastructure provider.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| apiServerInternalIPs are the IP addresses to contact the Kubernetes API server that can be used by components inside the cluster, like kubelets using the infrastructure rather than Kubernetes networking. These are the IPs for a self-hosted load balancer in front of the API servers. In dual stack clusters this list contains two IP addresses, one from IPv4 family and one from IPv6. In single stack clusters a single IP address is expected. When omitted, values from the status.apiServerInternalIPs will be used. Once set, the list cannot be completely removed (but its second entry can). |
|
| failureDomains contains the definition of region, zone and the vCenter topology. If this is omitted failure domains (regions and zones) will not be used. |
|
| VSpherePlatformFailureDomainSpec holds the region and zone failure domain and the vCenter topology of that failure domain. |
|
| ingressIPs are the external IPs which route to the default ingress controller. The IPs are suitable targets of a wildcard DNS record used to resolve default route host names. In dual stack clusters this list contains two IP addresses, one from IPv4 family and one from IPv6. In single stack clusters a single IP address is expected. When omitted, values from the status.ingressIPs will be used. Once set, the list cannot be completely removed (but its second entry can). |
|
| machineNetworks are IP networks used to connect all the OpenShift cluster nodes. Each network is provided in the CIDR format and should be IPv4 or IPv6, for example "10.0.0.0/8" or "fd00::/8". |
|
| nodeNetworking contains the definition of internal and external network constraints for assigning the node’s networking. If this field is omitted, networking defaults to the legacy address selection behavior which is to only support a single address and return the first one found. |
|
| vcenters holds the connection details for services to communicate with vCenter. Currently, only a single vCenter is supported. --- |
|
| VSpherePlatformVCenterSpec stores the vCenter connection fields. This is used by the vSphere CCM. |
15.1.31. .spec.platformSpec.vsphere.failureDomains
- Description
- failureDomains contains the definition of region, zone and the vCenter topology. If this is omitted failure domains (regions and zones) will not be used.
- Type
-
array
15.1.32. .spec.platformSpec.vsphere.failureDomains[]
- Description
- VSpherePlatformFailureDomainSpec holds the region and zone failure domain and the vCenter topology of that failure domain.
- Type
-
object
- Required
-
name
-
region
-
server
-
topology
-
zone
-
Property | Type | Description |
---|---|---|
|
| name defines the arbitrary but unique name of a failure domain. |
|
| region defines the name of a region tag that will be attached to a vCenter datacenter. The tag category in vCenter must be named openshift-region. |
|
| server is the fully-qualified domain name or the IP address of the vCenter server. --- |
|
| Topology describes a given failure domain using vSphere constructs |
|
| zone defines the name of a zone tag that will be attached to a vCenter cluster. The tag category in vCenter must be named openshift-zone. |
15.1.33. .spec.platformSpec.vsphere.failureDomains[].topology
- Description
- Topology describes a given failure domain using vSphere constructs
- Type
-
object
- Required
-
computeCluster
-
datacenter
-
datastore
-
networks
-
Property | Type | Description |
---|---|---|
|
| computeCluster the absolute path of the vCenter cluster in which virtual machine will be located. The absolute path is of the form /<datacenter>/host/<cluster>. The maximum length of the path is 2048 characters. |
|
| datacenter is the name of vCenter datacenter in which virtual machines will be located. The maximum length of the datacenter name is 80 characters. |
|
| datastore is the absolute path of the datastore in which the virtual machine is located. The absolute path is of the form /<datacenter>/datastore/<datastore> The maximum length of the path is 2048 characters. |
|
| folder is the absolute path of the folder where virtual machines are located. The absolute path is of the form /<datacenter>/vm/<folder>. The maximum length of the path is 2048 characters. |
|
|
networks is the list of port group network names within this failure domain. Currently, we only support a single interface per RHCOS virtual machine. The available networks (port groups) can be listed using |
|
| resourcePool is the absolute path of the resource pool where virtual machines will be created. The absolute path is of the form /<datacenter>/host/<cluster>/Resources/<resourcepool>. The maximum length of the path is 2048 characters. |
|
| template is the full inventory path of the virtual machine or template that will be cloned when creating new machines in this failure domain. The maximum length of the path is 2048 characters. When omitted, the template will be calculated by the control plane machineset operator based on the region and zone defined in VSpherePlatformFailureDomainSpec. For example, for zone=zonea, region=region1, and infrastructure name=test, the template path would be calculated as /<datacenter>/vm/test-rhcos-region1-zonea. |
15.1.34. .spec.platformSpec.vsphere.nodeNetworking
- Description
- nodeNetworking contains the definition of internal and external network constraints for assigning the node’s networking. If this field is omitted, networking defaults to the legacy address selection behavior which is to only support a single address and return the first one found.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| external represents the network configuration of the node that is externally routable. |
|
| internal represents the network configuration of the node that is routable only within the cluster. |
15.1.35. .spec.platformSpec.vsphere.nodeNetworking.external
- Description
- external represents the network configuration of the node that is externally routable.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| excludeNetworkSubnetCidr IP addresses in subnet ranges will be excluded when selecting the IP address from the VirtualMachine’s VM for use in the status.addresses fields. --- |
|
|
network VirtualMachine’s VM Network names that will be used to when searching for status.addresses fields. Note that if internal.networkSubnetCIDR and external.networkSubnetCIDR are not set, then the vNIC associated to this network must only have a single IP address assigned to it. The available networks (port groups) can be listed using |
|
| networkSubnetCidr IP address on VirtualMachine’s network interfaces included in the fields' CIDRs that will be used in respective status.addresses fields. --- |
15.1.36. .spec.platformSpec.vsphere.nodeNetworking.internal
- Description
- internal represents the network configuration of the node that is routable only within the cluster.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| excludeNetworkSubnetCidr IP addresses in subnet ranges will be excluded when selecting the IP address from the VirtualMachine’s VM for use in the status.addresses fields. --- |
|
|
network VirtualMachine’s VM Network names that will be used to when searching for status.addresses fields. Note that if internal.networkSubnetCIDR and external.networkSubnetCIDR are not set, then the vNIC associated to this network must only have a single IP address assigned to it. The available networks (port groups) can be listed using |
|
| networkSubnetCidr IP address on VirtualMachine’s network interfaces included in the fields' CIDRs that will be used in respective status.addresses fields. --- |
15.1.37. .spec.platformSpec.vsphere.vcenters
- Description
- vcenters holds the connection details for services to communicate with vCenter. Currently, only a single vCenter is supported. ---
- Type
-
array
15.1.38. .spec.platformSpec.vsphere.vcenters[]
- Description
- VSpherePlatformVCenterSpec stores the vCenter connection fields. This is used by the vSphere CCM.
- Type
-
object
- Required
-
datacenters
-
server
-
Property | Type | Description |
---|---|---|
|
| The vCenter Datacenters in which the RHCOS vm guests are located. This field will be used by the Cloud Controller Manager. Each datacenter listed here should be used within a topology. |
|
| port is the TCP port that will be used to communicate to the vCenter endpoint. When omitted, this means the user has no opinion and it is up to the platform to choose a sensible default, which is subject to change over time. |
|
| server is the fully-qualified domain name or the IP address of the vCenter server. --- |
15.1.39. .status
- Description
- status holds observed values from the cluster. They may not be overridden.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| apiServerInternalURL is a valid URI with scheme 'https', address and optionally a port (defaulting to 443). apiServerInternalURL can be used by components like kubelets, to contact the Kubernetes API server using the infrastructure provider rather than Kubernetes networking. |
|
| apiServerURL is a valid URI with scheme 'https', address and optionally a port (defaulting to 443). apiServerURL can be used by components like the web console to tell users where to find the Kubernetes API. |
|
| controlPlaneTopology expresses the expectations for operands that normally run on control nodes. The default is 'HighlyAvailable', which represents the behavior operators have in a "normal" cluster. The 'SingleReplica' mode will be used in single-node deployments and the operators should not configure the operand for highly-available operation The 'External' mode indicates that the control plane is hosted externally to the cluster and that its components are not visible within the cluster. |
|
| cpuPartitioning expresses if CPU partitioning is a currently enabled feature in the cluster. CPU Partitioning means that this cluster can support partitioning workloads to specific CPU Sets. Valid values are "None" and "AllNodes". When omitted, the default value is "None". The default value of "None" indicates that no nodes will be setup with CPU partitioning. The "AllNodes" value indicates that all nodes have been setup with CPU partitioning, and can then be further configured via the PerformanceProfile API. |
|
| etcdDiscoveryDomain is the domain used to fetch the SRV records for discovering etcd servers and clients. For more info: https://github.com/etcd-io/etcd/blob/329be66e8b3f9e2e6af83c123ff89297e49ebd15/Documentation/op-guide/clustering.md#dns-discovery deprecated: as of 4.7, this field is no longer set or honored. It will be removed in a future release. |
|
| infrastructureName uniquely identifies a cluster with a human friendly name. Once set it should not be changed. Must be of max length 27 and must have only alphanumeric or hyphen characters. |
|
|
infrastructureTopology expresses the expectations for infrastructure services that do not run on control plane nodes, usually indicated by a node selector for a |
|
| platform is the underlying infrastructure provider for the cluster. Deprecated: Use platformStatus.type instead. |
|
| platformStatus holds status information specific to the underlying infrastructure provider. |
15.1.40. .status.platformStatus
- Description
- platformStatus holds status information specific to the underlying infrastructure provider.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| AlibabaCloud contains settings specific to the Alibaba Cloud infrastructure provider. |
|
| AWS contains settings specific to the Amazon Web Services infrastructure provider. |
|
| Azure contains settings specific to the Azure infrastructure provider. |
|
| BareMetal contains settings specific to the BareMetal platform. |
|
| EquinixMetal contains settings specific to the Equinix Metal infrastructure provider. |
|
| External contains settings specific to the generic External infrastructure provider. |
|
| GCP contains settings specific to the Google Cloud Platform infrastructure provider. |
|
| IBMCloud contains settings specific to the IBMCloud infrastructure provider. |
|
| Kubevirt contains settings specific to the kubevirt infrastructure provider. |
|
| Nutanix contains settings specific to the Nutanix infrastructure provider. |
|
| OpenStack contains settings specific to the OpenStack infrastructure provider. |
|
| Ovirt contains settings specific to the oVirt infrastructure provider. |
|
| PowerVS contains settings specific to the Power Systems Virtual Servers infrastructure provider. |
|
|
type is the underlying infrastructure provider for the cluster. This value controls whether infrastructure automation such as service load balancers, dynamic volume provisioning, machine creation and deletion, and other integrations are enabled. If None, no infrastructure automation is enabled. Allowed values are "AWS", "Azure", "BareMetal", "GCP", "Libvirt", "OpenStack", "VSphere", "oVirt", "EquinixMetal", "PowerVS", "AlibabaCloud", "Nutanix" and "None". Individual components may not support all platforms, and must handle unrecognized platforms as None if they do not support that platform. This value will be synced with to the |
|
| VSphere contains settings specific to the VSphere infrastructure provider. |
15.1.41. .status.platformStatus.alibabaCloud
- Description
- AlibabaCloud contains settings specific to the Alibaba Cloud infrastructure provider.
- Type
-
object
- Required
-
region
-
Property | Type | Description |
---|---|---|
|
| region specifies the region for Alibaba Cloud resources created for the cluster. |
|
| resourceGroupID is the ID of the resource group for the cluster. |
|
| resourceTags is a list of additional tags to apply to Alibaba Cloud resources created for the cluster. |
|
| AlibabaCloudResourceTag is the set of tags to add to apply to resources. |
15.1.42. .status.platformStatus.alibabaCloud.resourceTags
- Description
- resourceTags is a list of additional tags to apply to Alibaba Cloud resources created for the cluster.
- Type
-
array
15.1.43. .status.platformStatus.alibabaCloud.resourceTags[]
- Description
- AlibabaCloudResourceTag is the set of tags to add to apply to resources.
- Type
-
object
- Required
-
key
-
value
-
Property | Type | Description |
---|---|---|
|
| key is the key of the tag. |
|
| value is the value of the tag. |
15.1.44. .status.platformStatus.aws
- Description
- AWS contains settings specific to the Amazon Web Services infrastructure provider.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| region holds the default AWS region for new AWS resources created by the cluster. |
|
| resourceTags is a list of additional tags to apply to AWS resources created for the cluster. See https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html for information on tagging AWS resources. AWS supports a maximum of 50 tags per resource. OpenShift reserves 25 tags for its use, leaving 25 tags available for the user. |
|
| AWSResourceTag is a tag to apply to AWS resources created for the cluster. |
|
| ServiceEndpoints list contains custom endpoints which will override default service endpoint of AWS Services. There must be only one ServiceEndpoint for a service. |
|
| AWSServiceEndpoint store the configuration of a custom url to override existing defaults of AWS Services. |
15.1.45. .status.platformStatus.aws.resourceTags
- Description
- resourceTags is a list of additional tags to apply to AWS resources created for the cluster. See https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html for information on tagging AWS resources. AWS supports a maximum of 50 tags per resource. OpenShift reserves 25 tags for its use, leaving 25 tags available for the user.
- Type
-
array
15.1.46. .status.platformStatus.aws.resourceTags[]
- Description
- AWSResourceTag is a tag to apply to AWS resources created for the cluster.
- Type
-
object
- Required
-
key
-
value
-
Property | Type | Description |
---|---|---|
|
| key is the key of the tag |
|
| value is the value of the tag. Some AWS service do not support empty values. Since tags are added to resources in many services, the length of the tag value must meet the requirements of all services. |
15.1.47. .status.platformStatus.aws.serviceEndpoints
- Description
- ServiceEndpoints list contains custom endpoints which will override default service endpoint of AWS Services. There must be only one ServiceEndpoint for a service.
- Type
-
array
15.1.48. .status.platformStatus.aws.serviceEndpoints[]
- Description
- AWSServiceEndpoint store the configuration of a custom url to override existing defaults of AWS Services.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| name is the name of the AWS service. The list of all the service names can be found at https://docs.aws.amazon.com/general/latest/gr/aws-service-information.html This must be provided and cannot be empty. |
|
| url is fully qualified URI with scheme https, that overrides the default generated endpoint for a client. This must be provided and cannot be empty. |
15.1.49. .status.platformStatus.azure
- Description
- Azure contains settings specific to the Azure infrastructure provider.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| armEndpoint specifies a URL to use for resource management in non-soverign clouds such as Azure Stack. |
|
|
cloudName is the name of the Azure cloud environment which can be used to configure the Azure SDK with the appropriate Azure API endpoints. If empty, the value is equal to |
|
| networkResourceGroupName is the Resource Group for network resources like the Virtual Network and Subnets used by the cluster. If empty, the value is same as ResourceGroupName. |
|
| resourceGroupName is the Resource Group for new Azure resources created for the cluster. |
|
| resourceTags is a list of additional tags to apply to Azure resources created for the cluster. See https://docs.microsoft.com/en-us/rest/api/resources/tags for information on tagging Azure resources. Due to limitations on Automation, Content Delivery Network, DNS Azure resources, a maximum of 15 tags may be applied. OpenShift reserves 5 tags for internal use, allowing 10 tags for user configuration. |
|
| AzureResourceTag is a tag to apply to Azure resources created for the cluster. |
15.1.50. .status.platformStatus.azure.resourceTags
- Description
- resourceTags is a list of additional tags to apply to Azure resources created for the cluster. See https://docs.microsoft.com/en-us/rest/api/resources/tags for information on tagging Azure resources. Due to limitations on Automation, Content Delivery Network, DNS Azure resources, a maximum of 15 tags may be applied. OpenShift reserves 5 tags for internal use, allowing 10 tags for user configuration.
- Type
-
array
15.1.51. .status.platformStatus.azure.resourceTags[]
- Description
- AzureResourceTag is a tag to apply to Azure resources created for the cluster.
- Type
-
object
- Required
-
key
-
value
-
Property | Type | Description |
---|---|---|
|
|
key is the key part of the tag. A tag key can have a maximum of 128 characters and cannot be empty. Key must begin with a letter, end with a letter, number or underscore, and must contain only alphanumeric characters and the following special characters |
|
|
value is the value part of the tag. A tag value can have a maximum of 256 characters and cannot be empty. Value must contain only alphanumeric characters and the following special characters |
15.1.52. .status.platformStatus.baremetal
- Description
- BareMetal contains settings specific to the BareMetal platform.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| apiServerInternalIP is an IP address to contact the Kubernetes API server that can be used by components inside the cluster, like kubelets using the infrastructure rather than Kubernetes networking. It is the IP that the Infrastructure.status.apiServerInternalURI points to. It is the IP for a self-hosted load balancer in front of the API servers. Deprecated: Use APIServerInternalIPs instead. |
|
| apiServerInternalIPs are the IP addresses to contact the Kubernetes API server that can be used by components inside the cluster, like kubelets using the infrastructure rather than Kubernetes networking. These are the IPs for a self-hosted load balancer in front of the API servers. In dual stack clusters this list contains two IPs otherwise only one. |
|
| ingressIP is an external IP which routes to the default ingress controller. The IP is a suitable target of a wildcard DNS record used to resolve default route host names. Deprecated: Use IngressIPs instead. |
|
| ingressIPs are the external IPs which route to the default ingress controller. The IPs are suitable targets of a wildcard DNS record used to resolve default route host names. In dual stack clusters this list contains two IPs otherwise only one. |
|
| loadBalancer defines how the load balancer used by the cluster is configured. |
|
| machineNetworks are IP networks used to connect all the OpenShift cluster nodes. |
|
|
nodeDNSIP is the IP address for the internal DNS used by the nodes. Unlike the one managed by the DNS operator, |
15.1.53. .status.platformStatus.baremetal.loadBalancer
- Description
- loadBalancer defines how the load balancer used by the cluster is configured.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| type defines the type of load balancer used by the cluster on BareMetal platform which can be a user-managed or openshift-managed load balancer that is to be used for the OpenShift API and Ingress endpoints. When set to OpenShiftManagedDefault the static pods in charge of API and Ingress traffic load-balancing defined in the machine config operator will be deployed. When set to UserManaged these static pods will not be deployed and it is expected that the load balancer is configured out of band by the deployer. When omitted, this means no opinion and the platform is left to choose a reasonable default. The default value is OpenShiftManagedDefault. |
15.1.54. .status.platformStatus.equinixMetal
- Description
- EquinixMetal contains settings specific to the Equinix Metal infrastructure provider.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| apiServerInternalIP is an IP address to contact the Kubernetes API server that can be used by components inside the cluster, like kubelets using the infrastructure rather than Kubernetes networking. It is the IP that the Infrastructure.status.apiServerInternalURI points to. It is the IP for a self-hosted load balancer in front of the API servers. |
|
| ingressIP is an external IP which routes to the default ingress controller. The IP is a suitable target of a wildcard DNS record used to resolve default route host names. |
15.1.55. .status.platformStatus.external
- Description
- External contains settings specific to the generic External infrastructure provider.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| cloudControllerManager contains settings specific to the external Cloud Controller Manager (a.k.a. CCM or CPI). When omitted, new nodes will be not tainted and no extra initialization from the cloud controller manager is expected. |
15.1.56. .status.platformStatus.external.cloudControllerManager
- Description
- cloudControllerManager contains settings specific to the external Cloud Controller Manager (a.k.a. CCM or CPI). When omitted, new nodes will be not tainted and no extra initialization from the cloud controller manager is expected.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| state determines whether or not an external Cloud Controller Manager is expected to be installed within the cluster. https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/#running-cloud-controller-manager Valid values are "External", "None" and omitted. When set to "External", new nodes will be tainted as uninitialized when created, preventing them from running workloads until they are initialized by the cloud controller manager. When omitted or set to "None", new nodes will be not tainted and no extra initialization from the cloud controller manager is expected. |
15.1.57. .status.platformStatus.gcp
- Description
- GCP contains settings specific to the Google Cloud Platform infrastructure provider.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| resourceGroupName is the Project ID for new GCP resources created for the cluster. |
|
| region holds the region for new GCP resources created for the cluster. |
15.1.58. .status.platformStatus.ibmcloud
- Description
- IBMCloud contains settings specific to the IBMCloud infrastructure provider.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| CISInstanceCRN is the CRN of the Cloud Internet Services instance managing the DNS zone for the cluster’s base domain |
|
| DNSInstanceCRN is the CRN of the DNS Services instance managing the DNS zone for the cluster’s base domain |
|
| Location is where the cluster has been deployed |
|
| ProviderType indicates the type of cluster that was created |
|
| ResourceGroupName is the Resource Group for new IBMCloud resources created for the cluster. |
|
| serviceEndpoints is a list of custom endpoints which will override the default service endpoints of an IBM Cloud service. These endpoints are consumed by components within the cluster to reach the respective IBM Cloud Services. |
|
| IBMCloudServiceEndpoint stores the configuration of a custom url to override existing defaults of IBM Cloud Services. |
15.1.59. .status.platformStatus.ibmcloud.serviceEndpoints
- Description
- serviceEndpoints is a list of custom endpoints which will override the default service endpoints of an IBM Cloud service. These endpoints are consumed by components within the cluster to reach the respective IBM Cloud Services.
- Type
-
array
15.1.60. .status.platformStatus.ibmcloud.serviceEndpoints[]
- Description
- IBMCloudServiceEndpoint stores the configuration of a custom url to override existing defaults of IBM Cloud Services.
- Type
-
object
- Required
-
name
-
url
-
Property | Type | Description |
---|---|---|
|
|
name is the name of the IBM Cloud service. Possible values are: CIS, COS, DNSServices, GlobalSearch, GlobalTagging, HyperProtect, IAM, KeyProtect, ResourceController, ResourceManager, or VPC. For example, the IBM Cloud Private IAM service could be configured with the service |
|
| url is fully qualified URI with scheme https, that overrides the default generated endpoint for a client. This must be provided and cannot be empty. |
15.1.61. .status.platformStatus.kubevirt
- Description
- Kubevirt contains settings specific to the kubevirt infrastructure provider.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| apiServerInternalIP is an IP address to contact the Kubernetes API server that can be used by components inside the cluster, like kubelets using the infrastructure rather than Kubernetes networking. It is the IP that the Infrastructure.status.apiServerInternalURI points to. It is the IP for a self-hosted load balancer in front of the API servers. |
|
| ingressIP is an external IP which routes to the default ingress controller. The IP is a suitable target of a wildcard DNS record used to resolve default route host names. |
15.1.62. .status.platformStatus.nutanix
- Description
- Nutanix contains settings specific to the Nutanix infrastructure provider.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| apiServerInternalIP is an IP address to contact the Kubernetes API server that can be used by components inside the cluster, like kubelets using the infrastructure rather than Kubernetes networking. It is the IP that the Infrastructure.status.apiServerInternalURI points to. It is the IP for a self-hosted load balancer in front of the API servers. Deprecated: Use APIServerInternalIPs instead. |
|
| apiServerInternalIPs are the IP addresses to contact the Kubernetes API server that can be used by components inside the cluster, like kubelets using the infrastructure rather than Kubernetes networking. These are the IPs for a self-hosted load balancer in front of the API servers. In dual stack clusters this list contains two IPs otherwise only one. |
|
| ingressIP is an external IP which routes to the default ingress controller. The IP is a suitable target of a wildcard DNS record used to resolve default route host names. Deprecated: Use IngressIPs instead. |
|
| ingressIPs are the external IPs which route to the default ingress controller. The IPs are suitable targets of a wildcard DNS record used to resolve default route host names. In dual stack clusters this list contains two IPs otherwise only one. |
|
| loadBalancer defines how the load balancer used by the cluster is configured. |
15.1.63. .status.platformStatus.nutanix.loadBalancer
- Description
- loadBalancer defines how the load balancer used by the cluster is configured.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| type defines the type of load balancer used by the cluster on Nutanix platform which can be a user-managed or openshift-managed load balancer that is to be used for the OpenShift API and Ingress endpoints. When set to OpenShiftManagedDefault the static pods in charge of API and Ingress traffic load-balancing defined in the machine config operator will be deployed. When set to UserManaged these static pods will not be deployed and it is expected that the load balancer is configured out of band by the deployer. When omitted, this means no opinion and the platform is left to choose a reasonable default. The default value is OpenShiftManagedDefault. |
15.1.64. .status.platformStatus.openstack
- Description
- OpenStack contains settings specific to the OpenStack infrastructure provider.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| apiServerInternalIP is an IP address to contact the Kubernetes API server that can be used by components inside the cluster, like kubelets using the infrastructure rather than Kubernetes networking. It is the IP that the Infrastructure.status.apiServerInternalURI points to. It is the IP for a self-hosted load balancer in front of the API servers. Deprecated: Use APIServerInternalIPs instead. |
|
| apiServerInternalIPs are the IP addresses to contact the Kubernetes API server that can be used by components inside the cluster, like kubelets using the infrastructure rather than Kubernetes networking. These are the IPs for a self-hosted load balancer in front of the API servers. In dual stack clusters this list contains two IPs otherwise only one. |
|
|
cloudName is the name of the desired OpenStack cloud in the client configuration file ( |
|
| ingressIP is an external IP which routes to the default ingress controller. The IP is a suitable target of a wildcard DNS record used to resolve default route host names. Deprecated: Use IngressIPs instead. |
|
| ingressIPs are the external IPs which route to the default ingress controller. The IPs are suitable targets of a wildcard DNS record used to resolve default route host names. In dual stack clusters this list contains two IPs otherwise only one. |
|
| loadBalancer defines how the load balancer used by the cluster is configured. |
|
| machineNetworks are IP networks used to connect all the OpenShift cluster nodes. |
|
|
nodeDNSIP is the IP address for the internal DNS used by the nodes. Unlike the one managed by the DNS operator, |
15.1.65. .status.platformStatus.openstack.loadBalancer
- Description
- loadBalancer defines how the load balancer used by the cluster is configured.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| type defines the type of load balancer used by the cluster on OpenStack platform which can be a user-managed or openshift-managed load balancer that is to be used for the OpenShift API and Ingress endpoints. When set to OpenShiftManagedDefault the static pods in charge of API and Ingress traffic load-balancing defined in the machine config operator will be deployed. When set to UserManaged these static pods will not be deployed and it is expected that the load balancer is configured out of band by the deployer. When omitted, this means no opinion and the platform is left to choose a reasonable default. The default value is OpenShiftManagedDefault. |
15.1.66. .status.platformStatus.ovirt
- Description
- Ovirt contains settings specific to the oVirt infrastructure provider.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| apiServerInternalIP is an IP address to contact the Kubernetes API server that can be used by components inside the cluster, like kubelets using the infrastructure rather than Kubernetes networking. It is the IP that the Infrastructure.status.apiServerInternalURI points to. It is the IP for a self-hosted load balancer in front of the API servers. Deprecated: Use APIServerInternalIPs instead. |
|
| apiServerInternalIPs are the IP addresses to contact the Kubernetes API server that can be used by components inside the cluster, like kubelets using the infrastructure rather than Kubernetes networking. These are the IPs for a self-hosted load balancer in front of the API servers. In dual stack clusters this list contains two IPs otherwise only one. |
|
| ingressIP is an external IP which routes to the default ingress controller. The IP is a suitable target of a wildcard DNS record used to resolve default route host names. Deprecated: Use IngressIPs instead. |
|
| ingressIPs are the external IPs which route to the default ingress controller. The IPs are suitable targets of a wildcard DNS record used to resolve default route host names. In dual stack clusters this list contains two IPs otherwise only one. |
|
| loadBalancer defines how the load balancer used by the cluster is configured. |
|
| deprecated: as of 4.6, this field is no longer set or honored. It will be removed in a future release. |
15.1.67. .status.platformStatus.ovirt.loadBalancer
- Description
- loadBalancer defines how the load balancer used by the cluster is configured.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| type defines the type of load balancer used by the cluster on Ovirt platform which can be a user-managed or openshift-managed load balancer that is to be used for the OpenShift API and Ingress endpoints. When set to OpenShiftManagedDefault the static pods in charge of API and Ingress traffic load-balancing defined in the machine config operator will be deployed. When set to UserManaged these static pods will not be deployed and it is expected that the load balancer is configured out of band by the deployer. When omitted, this means no opinion and the platform is left to choose a reasonable default. The default value is OpenShiftManagedDefault. |
15.1.68. .status.platformStatus.powervs
- Description
- PowerVS contains settings specific to the Power Systems Virtual Servers infrastructure provider.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| CISInstanceCRN is the CRN of the Cloud Internet Services instance managing the DNS zone for the cluster’s base domain |
|
| DNSInstanceCRN is the CRN of the DNS Services instance managing the DNS zone for the cluster’s base domain |
|
| region holds the default Power VS region for new Power VS resources created by the cluster. |
|
| resourceGroup is the resource group name for new IBMCloud resources created for a cluster. The resource group specified here will be used by cluster-image-registry-operator to set up a COS Instance in IBMCloud for the cluster registry. More about resource groups can be found here: https://cloud.ibm.com/docs/account?topic=account-rgs. When omitted, the image registry operator won’t be able to configure storage, which results in the image registry cluster operator not being in an available state. |
|
| serviceEndpoints is a list of custom endpoints which will override the default service endpoints of a Power VS service. |
|
| PowervsServiceEndpoint stores the configuration of a custom url to override existing defaults of PowerVS Services. |
|
| zone holds the default zone for the new Power VS resources created by the cluster. Note: Currently only single-zone OCP clusters are supported |
15.1.69. .status.platformStatus.powervs.serviceEndpoints
- Description
- serviceEndpoints is a list of custom endpoints which will override the default service endpoints of a Power VS service.
- Type
-
array
15.1.70. .status.platformStatus.powervs.serviceEndpoints[]
- Description
- PowervsServiceEndpoint stores the configuration of a custom url to override existing defaults of PowerVS Services.
- Type
-
object
- Required
-
name
-
url
-
Property | Type | Description |
---|---|---|
|
| name is the name of the Power VS service. Few of the services are IAM - https://cloud.ibm.com/apidocs/iam-identity-token-api ResourceController - https://cloud.ibm.com/apidocs/resource-controller/resource-controller Power Cloud - https://cloud.ibm.com/apidocs/power-cloud |
|
| url is fully qualified URI with scheme https, that overrides the default generated endpoint for a client. This must be provided and cannot be empty. |
15.1.71. .status.platformStatus.vsphere
- Description
- VSphere contains settings specific to the VSphere infrastructure provider.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| apiServerInternalIP is an IP address to contact the Kubernetes API server that can be used by components inside the cluster, like kubelets using the infrastructure rather than Kubernetes networking. It is the IP that the Infrastructure.status.apiServerInternalURI points to. It is the IP for a self-hosted load balancer in front of the API servers. Deprecated: Use APIServerInternalIPs instead. |
|
| apiServerInternalIPs are the IP addresses to contact the Kubernetes API server that can be used by components inside the cluster, like kubelets using the infrastructure rather than Kubernetes networking. These are the IPs for a self-hosted load balancer in front of the API servers. In dual stack clusters this list contains two IPs otherwise only one. |
|
| ingressIP is an external IP which routes to the default ingress controller. The IP is a suitable target of a wildcard DNS record used to resolve default route host names. Deprecated: Use IngressIPs instead. |
|
| ingressIPs are the external IPs which route to the default ingress controller. The IPs are suitable targets of a wildcard DNS record used to resolve default route host names. In dual stack clusters this list contains two IPs otherwise only one. |
|
| loadBalancer defines how the load balancer used by the cluster is configured. |
|
| machineNetworks are IP networks used to connect all the OpenShift cluster nodes. |
|
|
nodeDNSIP is the IP address for the internal DNS used by the nodes. Unlike the one managed by the DNS operator, |
15.1.72. .status.platformStatus.vsphere.loadBalancer
- Description
- loadBalancer defines how the load balancer used by the cluster is configured.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| type defines the type of load balancer used by the cluster on VSphere platform which can be a user-managed or openshift-managed load balancer that is to be used for the OpenShift API and Ingress endpoints. When set to OpenShiftManagedDefault the static pods in charge of API and Ingress traffic load-balancing defined in the machine config operator will be deployed. When set to UserManaged these static pods will not be deployed and it is expected that the load balancer is configured out of band by the deployer. When omitted, this means no opinion and the platform is left to choose a reasonable default. The default value is OpenShiftManagedDefault. |
15.2. API endpoints
The following API endpoints are available:
/apis/config.openshift.io/v1/infrastructures
-
DELETE
: delete collection of Infrastructure -
GET
: list objects of kind Infrastructure -
POST
: create an Infrastructure
-
/apis/config.openshift.io/v1/infrastructures/{name}
-
DELETE
: delete an Infrastructure -
GET
: read the specified Infrastructure -
PATCH
: partially update the specified Infrastructure -
PUT
: replace the specified Infrastructure
-
/apis/config.openshift.io/v1/infrastructures/{name}/status
-
GET
: read status of the specified Infrastructure -
PATCH
: partially update status of the specified Infrastructure -
PUT
: replace status of the specified Infrastructure
-
15.2.1. /apis/config.openshift.io/v1/infrastructures
- HTTP method
-
DELETE
- Description
- delete collection of Infrastructure
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- list objects of kind Infrastructure
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
POST
- Description
- create an Infrastructure
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
15.2.2. /apis/config.openshift.io/v1/infrastructures/{name}
Parameter | Type | Description |
---|---|---|
|
| name of the Infrastructure |
- HTTP method
-
DELETE
- Description
- delete an Infrastructure
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
HTTP code | Reponse body |
---|---|
200 - OK |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- read the specified Infrastructure
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update the specified Infrastructure
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace the specified Infrastructure
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
15.2.3. /apis/config.openshift.io/v1/infrastructures/{name}/status
Parameter | Type | Description |
---|---|---|
|
| name of the Infrastructure |
- HTTP method
-
GET
- Description
- read status of the specified Infrastructure
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update status of the specified Infrastructure
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace status of the specified Infrastructure
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |