IngressIstioController
Scope: Cluster
Version: v1alpha1
- objectspecRequired value - objectspec.hostPortHostPortinlet settings.- integerspec.hostPort.httpPortPort for insecure HTTP connections. If the parameter is not set, the connection over HTTP cannot be established. This parameter is mandatory if httpsPortis not set.Example: httpPort: 80
- integerspec.hostPort.httpsPortPort for secure HTTPS connections. If the parameter is not set, the connection over HTTPS cannot be established. This parameter is mandatory if httpPortis not set.Example: httpsPort: 443
 
- stringspec.ingressGatewayClassRequired value Ingress gateway class is used by application Gateway resources for identifying the right Ingress gateway setup. The identification is organized by setting the spec.selector: istio.deckhouse.io/ingress-gateway-class: <ingressGatewayClass value>.Pattern: ^[a-z0-9]([-a-z0-9]*[a-z0-9])?$Example: ingressGatewayClass: istio
- stringspec.inletRequired value The way traffic goes to cluster from the outer network. - LoadBalancer— Ingress controller is deployed and the service of- LoadBalancertype is provisioned.
- NodePort— Ingress controller is deployed and available through nodes’ ports via- nodePort.
- 
    HostPort— Ingress controller is deployed and available through nodes’ ports viahostPort.Caution! There can be only one controller with this inlet type on a host. 
 Allowed values: LoadBalancer,HostPort,NodePort
- objectspec.loadBalancerNot required value. A section of parameters of the LoadBalancerinlet.- objectspec.loadBalancer.annotationsAnnotations to assign to the service for flexible configuration of the load balancer. 
 
- objectspec.nodePortHostPortinlet settings.- integerspec.nodePort.httpPortPort for insecure HTTP connections. If the parameter is not set, the connection over HTTP cannot be established. This parameter is mandatory if httpsPortis not set.Example: httpPort: 30080
- integerspec.nodePort.httpsPortPort for secure HTTPS connections. If the parameter is not set, the connection over HTTPS cannot be established. This parameter is mandatory if httpPortis not set.Example: httpsPort: 30443
 
- objectspec.nodeSelectorThe same as in the pods’ spec.nodeSelectorparameter in Kubernetes.If the parameter is omitted or false, it will be determined automatically.Format: the standard nodeSelectorlist. Instance pods inherit this field as is.
- objectspec.resourcesRequestsMax amounts of CPU and memory resources that the pod can request when selecting a node (if the VPA is disabled, then these values become the default ones). - stringspec.resourcesRequests.modeRequired value The mode for managing resource requests. Default: VPAAllowed values: VPA,Static
- objectspec.resourcesRequests.staticStatic mode settings. - stringspec.resourcesRequests.static.cpuCPU requests. Default: 350m
- stringspec.resourcesRequests.static.memoryMemory requests. Default: 500Mi
 
- objectspec.resourcesRequests.vpaParameters of the vpa mode. - objectspec.resourcesRequests.vpa.cpuCPU-related parameters. - stringspec.resourcesRequests.vpa.cpu.maxMaximum allowed CPU requests. Default: 100m
- stringspec.resourcesRequests.vpa.cpu.minMinimum allowed CPU requests. Default: 50m
 
- objectspec.resourcesRequests.vpa.memoryThe amount of memory requested. - stringspec.resourcesRequests.vpa.memory.maxMaximum allowed memory requests. Default: 200Mi
- stringspec.resourcesRequests.vpa.memory.minMinimum allowed memory requests. Default: 100Mi
 
- stringspec.resourcesRequests.vpa.modeThe VPA usage mode. Default: InitialAllowed values: Initial,Auto
 
 
- array of objectsspec.tolerationsThe same as in the pods’ spec.tolerationsparameter in Kubernetes;If the parameter is omitted or false, it will be determined automatically.Format: the standard toleration list. Instance pods inherit this field as is. - stringspec.tolerations.effectAllowed values: NoSchedule,PreferNoSchedule,NoExecute
- stringspec.tolerations.key
- stringspec.tolerations.operatorDefault: EqualAllowed values: Exists,Equal
- integerspec.tolerations.tolerationSeconds
- stringspec.tolerations.value
 
 
IstioFederation
Scope: Cluster
Version: v1alpha1
Custom resource for setting remote cluster as trusted one.
- objectspecRequired value Available in editions: EE - objectspec.metadata- stringspec.metadata.caAvailable in editions: EE Certificate for validation HTTPS endpoint with remote cluster metadata. Example: ca: "-----BEGIN CERTIFICATE----- ..... -----END CERTIFICATE-----"
- booleanspec.metadata.insecureSkipVerifyAvailable in editions: EE Skip validation certificate on HTTPS endpoint with remote cluster metadata. Default: falseExample: insecureSkipVerify: 'true'
 
- stringspec.metadataEndpointRequired value Available in editions: EE HTTPS endpoint with remote cluster metadata. Pattern: ^https://[0-9a-zA-Z._/-]+$Example: metadataEndpoint: https://istio.k8s.example.com/metadata/
- stringspec.trustDomainRequired value Available in editions: EE The TrustDomain of the remote cluster. A mandatory parameter, but it is not currently utilized, as Istio does not yet support mapping TrustDomain to a root Certificate Authority (CA). Pattern: ^[0-9a-zA-Z._-]+$Example: trustDomain: cluster.local
 
IstioMulticluster
Scope: Cluster
Version: v1alpha1
Custom resource for setting remote cluster as trusted one.
- objectspecRequired value Available in editions: EE - booleanspec.enableIngressGatewayAvailable in editions: EE Using IngressGateway for accessing remote Pods. If remote Pods are accessible directly from our cluster (flat network), it is efficient not to use extra hop. Default: true
- objectspec.metadata- stringspec.metadata.caAvailable in editions: EE HTTPS certificate authority for remote cluster metadata. 
- booleanspec.metadata.insecureSkipVerifyAvailable in editions: EE HTTPS check or not for remote cluster metadata. Default: falseExample: insecureSkipVerify: 'true'
 
- stringspec.metadataEndpointRequired value Available in editions: EE HTTPS endpoint with remote cluster metadata. Pattern: ^https://[0-9a-zA-Z._/-]+$Example: metadataEndpoint: https://istio.k8s.example.com/metadata/