VmwareManualLbConfigArgs

data class VmwareManualLbConfigArgs(val controlPlaneNodePort: Output<Int>? = null, val ingressHttpNodePort: Output<Int>? = null, val ingressHttpsNodePort: Output<Int>? = null, val konnectivityServerNodePort: Output<Int>? = null) : ConvertibleToJava<VmwareManualLbConfigArgs>

Represents configuration parameters for an already existing manual load balancer. Given the nature of manual load balancers it is expected that said load balancer will be fully managed by users. IMPORTANT: Please note that the Anthos On-Prem API will not generate or update ManualLB configurations it can only bind a pre-existing configuration to a new VMware user cluster.

Constructors

Link copied to clipboard
constructor(controlPlaneNodePort: Output<Int>? = null, ingressHttpNodePort: Output<Int>? = null, ingressHttpsNodePort: Output<Int>? = null, konnectivityServerNodePort: Output<Int>? = null)

Properties

Link copied to clipboard
val controlPlaneNodePort: Output<Int>? = null

NodePort for control plane service. The Kubernetes API server in the admin cluster is implemented as a Service of type NodePort (ex. 30968).

Link copied to clipboard
val ingressHttpNodePort: Output<Int>? = null

NodePort for ingress service's http. The ingress service in the admin cluster is implemented as a Service of type NodePort (ex. 32527).

Link copied to clipboard
val ingressHttpsNodePort: Output<Int>? = null

NodePort for ingress service's https. The ingress service in the admin cluster is implemented as a Service of type NodePort (ex. 30139).

Link copied to clipboard
val konnectivityServerNodePort: Output<Int>? = null

NodePort for konnectivity server service running as a sidecar in each kube-apiserver pod (ex. 30564).

Functions

Link copied to clipboard
open override fun toJava(): VmwareManualLbConfigArgs