import { IDevKnativeNetworkingPkgApisNetworkingV1alpha1HTTPOption } from "./HTTPOption.js"; import { IDevKnativeNetworkingPkgApisNetworkingV1alpha1IngressRule } from "./IngressRule.js"; import { IDevKnativeNetworkingPkgApisNetworkingV1alpha1IngressTLS } from "./IngressTLS.js"; import { ModelData, Model } from "@kubernetes-models/base"; /** * IngressSpec describes the Ingress the user wishes to exist. * * In general this follows the same shape as K8s Ingress. * Some notable differences: * - Backends now can have namespace: * - Traffic can be split across multiple backends. * - Timeout & Retry can be configured. * - Headers can be appended. */ export interface IIngressSpec { /** * HTTPOption is the option of HTTP. It has the following two values: * `HTTPOptionEnabled`, `HTTPOptionRedirected` */ "httpOption"?: IDevKnativeNetworkingPkgApisNetworkingV1alpha1HTTPOption; /** * A list of host rules used to configure the Ingress. */ "rules"?: Array; /** * TLS configuration. Currently 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. */ "tls"?: Array; } /** * IngressSpec describes the Ingress the user wishes to exist. * * In general this follows the same shape as K8s Ingress. * Some notable differences: * - Backends now can have namespace: * - Traffic can be split across multiple backends. * - Timeout & Retry can be configured. * - Headers can be appended. */ export declare class IngressSpec extends Model implements IIngressSpec { "httpOption"?: IDevKnativeNetworkingPkgApisNetworkingV1alpha1HTTPOption; "rules"?: Array; "tls"?: Array; constructor(data?: ModelData); } export type { IIngressSpec as IDevKnativeNetworkingPkgApisNetworkingV1alpha1IngressSpec, IngressSpec as DevKnativeNetworkingPkgApisNetworkingV1alpha1IngressSpec };