pulumi-kubernetes-kotlin/com.pulumi.kubernetes.networking.v1beta1.kotlin.inputs/IngressSpecPatchArgs

IngressSpecPatchArgs

data class IngressSpecPatchArgs(val backend: Output<IngressBackendPatchArgs>? = null, val ingressClassName: Output<String>? = null, val rules: Output<List<IngressRulePatchArgs>>? = null, val tls: Output<List<IngressTLSPatchArgs>>? = null) : ConvertibleToJava<IngressSpecPatchArgs>

IngressSpec describes the Ingress the user wishes to exist.

Constructors

fun IngressSpecPatchArgs(backend: Output<IngressBackendPatchArgs>? = null, ingressClassName: Output<String>? = null, rules: Output<List<IngressRulePatchArgs>>? = null, tls: Output<List<IngressTLSPatchArgs>>? = null)

Functions

toJava

open override fun toJava(): IngressSpecPatchArgs

Properties

backend

val backend: Output<IngressBackendPatchArgs>? = null

A default backend capable of servicing requests that don't match any rule. At least one of 'backend' or 'rules' must be specified. This field is optional to allow the loadbalancer controller or defaulting logic to specify a global default.

ingressClassName

val ingressClassName: Output<String>? = null

IngressClassName is the name of the IngressClass cluster resource. The associated IngressClass defines which controller will implement the resource. This replaces the deprecated kubernetes.io/ingress.class annotation. For backwards compatibility, when that annotation is set, it must be given precedence over this field. The controller may emit a warning if the field and annotation have different values. Implementations of this API should ignore Ingresses without a class specified. An IngressClass resource may be marked as default, which can be used to set a default value for this field. For more information, refer to the IngressClass documentation.

rules

val rules: Output<List<IngressRulePatchArgs>>? = null

A list of host rules used to configure the Ingress. If unspecified, or no rule matches, all traffic is sent to the default backend.

tls

val tls: Output<List<IngressTLSPatchArgs>>? = null

TLS configuration. Currently the Ingress only supports a single TLS port, 443. If multiple members of this list specify different hosts, they will be multiplexed on the same port according to the hostname specified through the SNI TLS extension, if the ingress controller fulfilling the ingress supports SNI.