The Deckhouse Platform installs CRDs but does not remove them when a module is disabled. If you no longer need the created CRDs, delete them.
The module lifecycle stage: General Availability
The module has requirements for installation
IngressIstioController
Scope: Cluster
Version: v1alpha1
- objectspec
Required value
- objectspec.hostPort
HostPortinlet settings.- integerspec.hostPort.httpPort
Port 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.httpsPort
Port 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.ingressGatewayClass
Required 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>.This parameter does not change during the entire resource life.
Pattern:
^[a-z0-9]([-a-z0-9]*[a-z0-9])?$Maximum length:
63Example:
ingressGatewayClass: istio - stringspec.inlet
Required value
The way traffic goes to cluster from the outer network.
LoadBalancer— Ingress controller is deployed and the service ofLoadBalancertype is provisioned.NodePort— Ingress controller is deployed and available through nodes’ ports vianodePort.-
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.loadBalancer
Not required value.
A section of parameters of the
LoadBalancerinlet.- objectspec.loadBalancer.annotations
Annotations to assign to the service for flexible configuration of the load balancer.
- stringspec.loadBalancer.loadBalancerClass
Class of the load balancer for incoming network requests (passed to the
spec.loadBalancerClassparameter of the provisioned service with theLoadBalancertype).
- objectspec.networkTopology
Configures how the gateway extracts the client’s original attributes (e.g. the source IP address) when it is deployed behind other proxies or load balancers.
See Configuring Gateway Network Topology in the Istio documentation.
- integerspec.networkTopology.numTrustedProxies
Number of trusted proxies deployed in front of the Istio gateway proxy.
It is used to correctly extract the client address from the
X-Forwarded-Forheader and populate theX-Envoy-External-Addressheader consumed by upstream services.For example, if there is a cloud load balancer and a reverse proxy in front of the gateway, set this to
2.It can be used with
proxyProtocol. When both are configured and an incoming request contains anX-Forwarded-Forheader, Istio uses the trustedX-Forwarded-Forchain in preference to the PROXY protocol attributes.Allowed values:
0 <= XExample:
numTrustedProxies: 2 - booleanspec.networkTopology.proxyProtocol
Enables the PROXY protocol on the gateway’s TCP listeners, so that client attributes (such as the source IP) forwarded by an upstream L4/TCP load balancer are preserved.
It can be used with
numTrustedProxies. When both are configured and an incoming request contains anX-Forwarded-Forheader, Istio uses the trustedX-Forwarded-Forchain in preference to the PROXY protocol attributes.Example:
proxyProtocol: true
- objectspec.nodePort
NodePortinlet settings.- integerspec.nodePort.httpPort
Port 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.httpsPort
Port 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.nodeSelector
The 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.resourcesRequests
Settings for CPU and memory requests and limits by ingress gateway pods.
If omitted, the built-in VPA mode defaults are used. In
Staticmode, requests are specified directly instatic. InVPAmode, the VPA adjusts requests within the configured minimum and maximum bounds.- stringspec.resourcesRequests.mode
Required value
Resource management mode:
Static— allows you to specify requests directly in thestaticsection;VPA— uses VPA. You can configure this mode by modifying parameters in thevpasection.
Default:
VPAAllowed values:
VPA,Static - objectspec.resourcesRequests.static
Resource management options for the
Staticmode.- stringspec.resourcesRequests.static.cpu
Configuring CPU requests.
Default:
100m - stringspec.resourcesRequests.static.memory
Configuring memory requests.
Default:
128Mi
- objectspec.resourcesRequests.vpa
Resource management options for the
VPAmode.- objectspec.resourcesRequests.vpa.cpu
CPU-related VPA settings.
- stringspec.resourcesRequests.vpa.cpu.max
The maximum value that the VPA can set for the CPU requests.
Default:
1000m - stringspec.resourcesRequests.vpa.cpu.min
The minimum value that the VPA can set for the CPU requests.
Default:
100m
- objectspec.resourcesRequests.vpa.memory
Memory-related VPA settings.
- stringspec.resourcesRequests.vpa.memory.max
The maximum memory requests the VPA can set.
Default:
2048Mi - stringspec.resourcesRequests.vpa.memory.min
The minimum memory requests the VPA can set.
Default:
128Mi
- stringspec.resourcesRequests.vpa.mode
VPA operating mode.
-
Initial— VPA sets initial values for pod resource requests at pod creation time. Resource values are not changed automatically afterwards. -
InPlaceOrRecreate— VPA attempts to update pod resources in place when supported by the cluster. If in-place updates are not possible, the pod is recreated. -
Auto— VPA automatically recreates pods to apply updated resource values. This mode is considered legacy starting from Deckhouse version 1.75;InPlaceOrRecreateis recommended.
Default:
InitialAllowed values:
Initial,InPlaceOrRecreate,Auto -
- array of objectsspec.tolerations
The 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.effect
Allowed values:
NoSchedule,PreferNoSchedule,NoExecute - stringspec.tolerations.key
- stringspec.tolerations.operator
Default:
EqualAllowed values:
Exists,Equal - integerspec.tolerations.tolerationSeconds
- stringspec.tolerations.value
IstioFederation
Scope: Cluster
Version: v1alpha1
Custom resource for setting remote cluster as trusted one.
- objectspec
Required value
Available in editions: Ultimate/EE
- objectspec.metadata
- stringspec.metadata.ca
Available in editions: Ultimate/EE
Certificate for validation HTTPS endpoint with remote cluster metadata.
Example:
ca: "-----BEGIN CERTIFICATE----- ..... -----END CERTIFICATE-----" - booleanspec.metadata.insecureSkipVerify
Available in editions: Ultimate/EE
Skip validation certificate on HTTPS endpoint with remote cluster metadata.
Default:
falseExample:
insecureSkipVerify: true
- stringspec.metadataEndpoint
Required value
Available in editions: Ultimate/EE
HTTPS endpoint with remote cluster metadata.
Example:
metadataEndpoint: https://istio.k8s.example.com/metadata/ - stringspec.trustDomain
Required value
Available in editions: Ultimate/EE
The TrustDomain of the remote cluster.
Deckhouse uses this value so that certificates from the remote cluster are trusted only for that remote domain, not for services in the local mesh.
Pattern:
^[0-9a-zA-Z._-]+$Example:
trustDomain: cluster.local
- objectstatus
- array of objectsstatus.conditions
Readiness of metadata exchange with the remote cluster.
If
spec.trustDomainequals the domain of this cluster, the resource does not take part in the federation: once the public metadata exchange succeeds, private metadata is not requested andPrivateMetadataExchangeReadyisFalsewith reasonClusterDomainMismatch; the remote cluster getsUnknownSourceClusterfrom this cluster.PublicMetadataExchangeReady— remotepublic.jsonis reachable and valid. Reasons:Succeeded(True) — the remote public metadata is received.FetchFailed(False) — the request to the metadata endpoint failed: network, DNS, timeout, TLS, a 3xx redirect (redirects are not allowed), an address resolving to a restricted IP (loopback, link-local, unspecified, multicast), a response larger than 1 MiB. The error is inmessage.EndpointNotFound(False) — HTTP 404:metadataEndpointmost likely does not point to the remote exporter, or the remote cluster has both federation and multicluster disabled.ServerError(False) — HTTP 5xx: the remote exporter or its ingress is unavailable.AccessDenied(False) — HTTP 401 or 403: something on the way to the remote exporter (an ingress or a proxy with access restrictions) refused the request; the code is inmessage.UnexpectedHTTPStatus(False) — another non-200 HTTP status; the code is inmessage.InvalidJSON(False) — the response is not valid JSON; check thatmetadataEndpointpoints to the remote exporter.InvalidPublicMetadata(False) — the remotepublic.jsonlacksclusterUUID,authnKeyPuborrootCA.ClusterUUIDMismatch(False) — the UUID returned by the endpoint differs fromstatus.metadataCache.public.clusterUUID: the remote cluster was recreated ormetadataEndpointnow points to another cluster. Both UUIDs are inmessage.
PrivateMetadataExchangeReady— remote private metadata is reachable and valid. Reasons:AwaitingPublic(Unknown) — the public metadata exchange is failing (seePublicMetadataExchangeReady), so private metadata is not requested.TokenGenerationFailed(False) — the request could not be signed with the authn key of this cluster; check the key Secret in this cluster.FetchFailed(False) — the request to the private endpoint failed: network, DNS, timeout, TLS, a 3xx redirect, a restricted IP, a response larger than 1 MiB. The error is inmessage.UnknownSourceCluster(False) — the remote cluster does not know this cluster: it has no resource for this cluster, the public metadata exchange of that resource has never succeeded (ClusterUUIDMismatchthere means this cluster was recreated, so the remote resource has to be recreated), or that resource is anIstioFederationwhosespec.trustDomainequals the domain of the remote cluster (it showsClusterDomainMismatchthere).TrustLost(False) — the same refusal asUnknownSourceCluster, but this cluster has already received private metadata from the remote one: the remote resource for this cluster was deleted, recreated or became ignored, or the authn key of this cluster changed. After a recreation or a key change the condition clears within a couple of minutes once the remote cluster fetches the public metadata of this cluster.WrongAllianceKind(False) — the remote cluster registered this cluster asIstioMulticluster, notIstioFederation; replace it with anIstioFederationon the remote side.EndpointNotFound(False) — HTTP 404: the public endpoint responded, so the remote cluster most likely has federation disabled (federation.enabled).ServerError(False) — HTTP 5xx: the remote exporter failed on the private path.ClusterDomainMismatch(False) — federation requires different cluster domains: eitherspec.trustDomainequals the domain of this cluster (private metadata is not requested; setspec.trustDomainto the domain of the remote cluster), or the remote cluster reports the domain of this cluster in its private metadata (not checked if the remote cluster does not publish its domain). The domain is inmessage.WrongJWTAudience(False) — the remote cluster rejected the token as issued for another cluster: the public and private requests were served by different clusters (DNS, a load balancer or a proxy leads to several clusters).TokenExpired(False) — the token has expired because the clocks differ; check time synchronization (NTP) on both clusters.InvalidToken(False) — the remote cluster did not receive or could not parse the token: a proxy or ingress on the way strips theAuthorizationheader, or a platform error.WrongJWTScope(False) — the token was issued for another private path: a platform error or a proxy rewriting the path.AccessDenied(False) — HTTP 401 or 403 without a machine-readable reason: the remote exporter is of an older version and does not tell why (most often it does not know this cluster), or an ingress or a proxy on the way refused the request; the code is inmessage.UnexpectedHTTPStatus(False) — another non-200 HTTP status; the code is inmessage.InvalidJSON(False) — the remote private response is not valid JSON.InvalidPrivateMetadata(False) — the remote private metadata has nopublicServices.MissingIngressGateways(False) — the remote cluster published no ingress gateway addresses (usually its LoadBalancer has no address yet, or the remote exporter failed to collect them). The private metadata fetched last, including the gateway addresses, stays in use.Succeeded(True) — the remote private metadata is received.
DataplaneConnectionReady— cross-cluster dataplane health probe to the remotealliance-healthcheckservice succeeded. Reasons:AwaitingPublic(Unknown) —status.metadataCachehas no public metadata yet.AwaitingPrivate(Unknown) —status.metadataCachehas public metadata but no private metadata yet. For a new connection the state is kept for one or two probe cycles (up to about two minutes) after the private metadata is received, so that the mesh applies it before the first probe.ProbeFailed(False) — the probe through the remote ingress gateway fails;messagehas the request error or the HTTP status code. With a remote cluster on an older module version (it neither checks the resource kind nor publishes its domain), a wrong resource kind on the remote side or equal cluster domains withspec.trustDomainset to another domain show up only here.ConfigurationError(False) — the private metadata is received, but the remotepublicServiceshas noalliance-healthcheckservice (for example, the remote istio module version is older). Details are inmessage.MetadataUnavailable(False) — platform error: the remote cluster UUID cannot be read from the cached metadata.Succeeded(True) — the dataplane connection to the remote cluster works.
- stringstatus.conditions.lastProbeTime
Required value
- stringstatus.conditions.lastTransitionTime
Required value
- stringstatus.conditions.message
Required value
- stringstatus.conditions.reason
Required value
- stringstatus.conditions.status
Required value
Allowed values:
True,False,Unknown - stringstatus.conditions.type
Required value
- objectstatus.metadataCache
- objectstatus.metadataCache.private
- stringstatus.metadataCache.private.clusterDomain
- array of objectsstatus.metadataCache.private.ingressGateways
- stringstatus.metadataCache.private.ingressGateways.address
- integerstatus.metadataCache.private.ingressGateways.port
- array of objectsstatus.metadataCache.private.publicServices
- stringstatus.metadataCache.private.publicServices.hostname
- array of objectsstatus.metadataCache.private.publicServices.ports
- stringstatus.metadataCache.private.publicServices.ports.name
- integerstatus.metadataCache.private.publicServices.ports.port
- stringstatus.metadataCache.private.publicServices.ports.protocol
- objectstatus.metadataCache.public
- stringstatus.metadataCache.public.authnKeyPub
- stringstatus.metadataCache.public.clusterUUID
- stringstatus.metadataCache.public.rootCA
IstioMulticluster
Scope: Cluster
Version: v1alpha1
Custom resource for setting remote cluster as trusted one.
- objectspec
Required value
Available in editions: Ultimate/EE
- booleanspec.enableIngressGateway
Available in editions: Ultimate/EE
Whether to reach the pods of the remote cluster through its ingress gateway.
If the pods of the clusters are directly reachable from each other (flat network), set it to
falseto avoid the extra hop through the ingress gateway.Set the same value on both sides: in the remote cluster, in the IstioMulticluster that describes this cluster. A cluster deploys its ingress gateway only if federation is enabled or at least one IstioMulticluster in it has
enableIngressGateway: true. Iffalseis set on one side only, the other side may find no ingress gateway to connect through (theIngressGatewayNotDeployedreason instatus.conditions).Default:
true - objectspec.metadata
- stringspec.metadata.ca
Available in editions: Ultimate/EE
HTTPS certificate authority for remote cluster metadata.
- booleanspec.metadata.insecureSkipVerify
Available in editions: Ultimate/EE
HTTPS check or not for remote cluster metadata.
Default:
falseExample:
insecureSkipVerify: true
- stringspec.metadataEndpoint
Required value
Available in editions: Ultimate/EE
HTTPS endpoint with remote cluster metadata.
Example:
metadataEndpoint: https://istio.k8s.example.com/metadata/
- objectstatus
- array of objectsstatus.conditions
Readiness of metadata exchange with the remote cluster.
PublicMetadataExchangeReady— remotepublic.jsonis reachable and valid. Reasons:Succeeded(True) — the remote public metadata is received.FetchFailed(False) — the request to the metadata endpoint failed: network, DNS, timeout, TLS, a 3xx redirect (redirects are not allowed), an address resolving to a restricted IP (loopback, link-local, unspecified, multicast), a response larger than 1 MiB. The error is inmessage.EndpointNotFound(False) — HTTP 404:metadataEndpointmost likely does not point to the remote exporter, or the remote cluster has both federation and multicluster disabled.ServerError(False) — HTTP 5xx: the remote exporter or its ingress is unavailable.AccessDenied(False) — HTTP 401 or 403: something on the way to the remote exporter (an ingress or a proxy with access restrictions) refused the request; the code is inmessage.UnexpectedHTTPStatus(False) — another non-200 HTTP status; the code is inmessage.InvalidJSON(False) — the response is not valid JSON; check thatmetadataEndpointpoints to the remote exporter.InvalidPublicMetadata(False) — the remotepublic.jsonlacksclusterUUID,authnKeyPuborrootCA.ClusterUUIDMismatch(False) — the UUID returned by the endpoint differs fromstatus.metadataCache.public.clusterUUID: the remote cluster was recreated ormetadataEndpointnow points to another cluster. Both UUIDs are inmessage.
PrivateMetadataExchangeReady— remote private metadata is reachable and valid. Reasons:AwaitingPublic(Unknown) — the public metadata exchange is failing (seePublicMetadataExchangeReady), so private metadata is not requested.TokenGenerationFailed(False) — the request could not be signed with the authn key of this cluster; check the key Secret in this cluster.FetchFailed(False) — the request to the private endpoint failed: network, DNS, timeout, TLS, a 3xx redirect, a restricted IP, a response larger than 1 MiB. The error is inmessage.UnknownSourceCluster(False) — the remote cluster does not know this cluster: it has no resource for this cluster, the public metadata exchange of that resource has never succeeded (ClusterUUIDMismatchthere means this cluster was recreated, so the remote resource has to be recreated), or the remote cluster has anIstioFederationfor this cluster instead of anIstioMulticluster(with equal domains, as multicluster requires, it is ignored there, so the wrong kind shows up here and not asWrongAllianceKind).TrustLost(False) — the same refusal asUnknownSourceCluster, but this cluster has already received private metadata from the remote one: the remote resource for this cluster was deleted, recreated or became ignored, or the authn key of this cluster changed. After a recreation or a key change the condition clears within a couple of minutes once the remote cluster fetches the public metadata of this cluster.WrongAllianceKind(False) — the remote cluster registered this cluster asIstioFederation, notIstioMulticluster; replace it with anIstioMulticlusteron the remote side.EndpointNotFound(False) — HTTP 404: the public endpoint responded, so the remote cluster most likely has multicluster disabled (multicluster.enabled).ServerError(False) — HTTP 5xx: the remote exporter failed on the private path.ClusterDomainMismatch(False) — the remote cluster domain differs from the domain of this cluster, while multicluster requires equal domains. Both domains are inmessage. Not checked if the remote cluster does not publish its domain.WrongJWTAudience(False) — the remote cluster rejected the token as issued for another cluster: the public and private requests were served by different clusters (DNS, a load balancer or a proxy leads to several clusters).TokenExpired(False) — the token has expired because the clocks differ; check time synchronization (NTP) on both clusters.InvalidToken(False) — the remote cluster did not receive or could not parse the token: a proxy or ingress on the way strips theAuthorizationheader, or a platform error.WrongJWTScope(False) — the token was issued for another private path: a platform error or a proxy rewriting the path.AccessDenied(False) — HTTP 401 or 403 without a machine-readable reason: the remote exporter is of an older version and does not tell why (most often it does not know this cluster), or an ingress or a proxy on the way refused the request; the code is inmessage.UnexpectedHTTPStatus(False) — another non-200 HTTP status; the code is inmessage.InvalidJSON(False) — the remote private response is not valid JSON.InvalidPrivateMetadata(False) — the remote private metadata has an emptynetworkNameorapiHost.MissingIngressGateways(False) —spec.enableIngressGatewayistrue, but the remote cluster published no ingress gateway addresses (usually its LoadBalancer has no address yet, or the remote exporter failed to collect them). A remote cluster on an older module version that deploys no ingress gateway is also reported with this reason, not withIngressGatewayNotDeployed. The private metadata fetched last, including the gateway addresses, stays in use.IngressGatewayNotDeployed(False) —spec.enableIngressGatewayistrue, but the remote cluster deploys no ingress gateway. Most often, the IstioMulticluster that describes this cluster in the remote cluster hasspec.enableIngressGateway: false, and nothing else there needs the ingress gateway (seespec.enableIngressGateway);messagelists what else to check in the remote cluster. The cached addresses are cleared, and this cluster does not connect to the remote cluster until this is fixed.Succeeded(True) — the remote private metadata is received.
RemoteAPIServerReady— remote multicluster API host (apiHost) serves the authenticated/apiendpoint. Reasons:AwaitingPrivate(Unknown) — the private metadata exchange has not succeeded yet (seePrivateMetadataExchangeReady), including while the public metadata exchange fails.TokenGenerationFailed(False) — the API token could not be signed with the authn key of this cluster; check the key Secret in this cluster.MissingAPIHost(False) — the remoteapiHostconsists only of whitespace (an emptyapiHostis reported asInvalidPrivateMetadataonPrivateMetadataExchangeReady).RemoteAPIUnreachable(False) — the request to the remote API failed: network, DNS, timeout, TLS, a redirect, a non-HTTPSapiHost, a restricted IP, a response larger than 1 MiB. The error is inmessage.RemoteAPIBadResponse(False) — the remote API returned a non-200 HTTP status (the code is inmessage); check the remote api-proxy and its permissions.RemoteAPIInvalidResponse(False) — the remote API response is not valid JSON; check thatapiHostpoints to the remote api-proxy.RemoteAPIUnexpectedResponse(False) —apiHostdoes not serve the Kubernetes API (the response kind is notAPIVersions).RemoteAPIReachable(True) — the remote API server is reachable.
DataplaneConnectionReady— cross-cluster dataplane health probe to the remotealliance-healthcheckservice succeeded. Reasons:AwaitingPublic(Unknown) —status.metadataCachehas no public metadata yet.AwaitingPrivate(Unknown) —status.metadataCachehas public metadata but no private metadata yet. For a new connection the state is kept for one or two probe cycles (up to about two minutes) after the private metadata is received, so that the mesh applies it before the first probe.ProbeFailed(False) — the probe to the remotealliance-healthcheckservice fails (through the remote ingress gateway, or directly to remote Pods whenspec.enableIngressGatewayisfalse);messagehas the request error or the HTTP status code. With a remote cluster on an older module version, a wrong resource kind or different cluster domains show up only here.MetadataUnavailable(False) — platform error: the remote cluster UUID cannot be read from the cached metadata.Succeeded(True) — the dataplane connection to the remote cluster works.
- stringstatus.conditions.lastProbeTime
Required value
- stringstatus.conditions.lastTransitionTime
Required value
- stringstatus.conditions.message
Required value
- stringstatus.conditions.reason
Required value
- stringstatus.conditions.status
Required value
Allowed values:
True,False,Unknown - stringstatus.conditions.type
Required value
- objectstatus.metadataCache
- objectstatus.metadataCache.private
- array of objectsstatus.metadataCache.private.ambientGateways
- stringstatus.metadataCache.private.ambientGateways.address
- integerstatus.metadataCache.private.ambientGateways.port
- stringstatus.metadataCache.private.apiHost
- stringstatus.metadataCache.private.ca
- stringstatus.metadataCache.private.clusterDomain
- stringstatus.metadataCache.private.clusterID
- array of objectsstatus.metadataCache.private.ingressGateways
- stringstatus.metadataCache.private.ingressGateways.address
- integerstatus.metadataCache.private.ingressGateways.port
- stringstatus.metadataCache.private.networkName
- objectstatus.metadataCache.public
- stringstatus.metadataCache.public.authnKeyPub
- stringstatus.metadataCache.public.clusterUUID
- stringstatus.metadataCache.public.rootCA
WaypointInstance
Short names: wpi
Scope: Namespaced
Version: v1alpha1
- objectmetadata
- stringmetadata.name
Pattern:
^[a-z0-9]([-a-z0-9]*[a-z0-9])?$Maximum length:
51
- objectspec
- objectspec.allowedRoutes
Configuration for restricting which Routes can attach to the Gateway.
- objectspec.allowedRoutes.namespaces
Configuration for restricting the namespaces of Routes that can attach to the Gateway.
- stringspec.allowedRoutes.namespaces.from
Specifies which namespaces are allowed to attach Routes to this Gateway.
Possible values:
All: Routes in all namespaces may be attached.Selector: Only Routes in namespaces matching theselectormay be attached.Same: Only Routes in the same namespace as the Gateway may be attached.
Default:
SameAllowed values:
All,Selector,Same - objectspec.allowedRoutes.namespaces.selector
Label selector for selecting namespaces.
Required when
fromisSelector.- array of objectsspec.allowedRoutes.namespaces.selector.matchExpressions
A list of label selector requirements.
- stringspec.allowedRoutes.namespaces.selector.matchExpressions.key
Required value
- stringspec.allowedRoutes.namespaces.selector.matchExpressions.operator
Required value
Allowed values:
In,NotIn,Exists,DoesNotExist - array of stringsspec.allowedRoutes.namespaces.selector.matchExpressions.values
- objectspec.allowedRoutes.namespaces.selector.matchLabels
A map of {key,value} pairs.
A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions with operator
Inand the values array containing only the value.
- objectspec.nodeSelector
Node selector for waypoint proxy pods.
- objectspec.replicasManagement
Replication management settings and scaling for the waypoint instance.
- objectspec.replicasManagement.hpa
Options for replicas management for the
HPAmode.- integerspec.replicasManagement.hpa.maxReplicas
The upper limit for the number of replicas to which the HPA can scale up.
Allowed values:
1 <= X - array of objectsspec.replicasManagement.hpa.metrics
The HPA will use these metrics to decide whether to increase or decrease the number of replicas.
- integerspec.replicasManagement.hpa.metrics.targetAverageUtilization
Required value
The target value of the average resource metric across all relevant pods, represented as a percentage of the requested value.
Allowed values:
1 <= X <= 100 - stringspec.replicasManagement.hpa.metrics.type
Required value
Metric type.
Allowed values:
CPU
- integerspec.replicasManagement.hpa.minReplicas
The lower limit for the number of replicas to which the HPA can scale down.
Allowed values:
1 <= X
- stringspec.replicasManagement.mode
Replicas management mode.
Possible values:
Static: the mode where the number of replicas is specified explicitly.HPA: the mode where the number of replicas is calculated automatically using HPA based on CPU usage.
Default:
StaticAllowed values:
Static,HPA - objectspec.replicasManagement.static
Options for replicas management for the
Staticmode.- integerspec.replicasManagement.static.replicas
Desired number of replicas.
Allowed values:
1 <= X
- objectspec.resourcesManagement
CPU and memory request and limit settings for the waypoint Pods.
- stringspec.resourcesManagement.mode
Resource management mode.
Default:
VPAAllowed values:
VPA,Static - objectspec.resourcesManagement.static
Static mode settings.
- objectspec.resourcesManagement.static.limits
Resource limits.
- stringspec.resourcesManagement.static.limits.cpu
CPU limits.
- stringspec.resourcesManagement.static.limits.memory
Memory limits.
- objectspec.resourcesManagement.static.requests
Resource requests.
- stringspec.resourcesManagement.static.requests.cpu
CPU requests.
Default:
100m - stringspec.resourcesManagement.static.requests.memory
Memory requests.
Default:
128Mi
- objectspec.resourcesManagement.vpa
Resource management settings for the VPA mode.
- objectspec.resourcesManagement.vpa.cpu
CPU-related VPA settings.
- numberspec.resourcesManagement.vpa.cpu.limitRatio
The CPU limits/requests ratio.
If set, the limits are calculated based on the requests and the specified ratio.
- stringspec.resourcesManagement.vpa.cpu.max
Maximum value of allowed CPU requests to be submitted by the VPA.
Default:
1000m - stringspec.resourcesManagement.vpa.cpu.min
Minimum value of allowed CPU requests to be submitted by the VPA.
Default:
100m
- objectspec.resourcesManagement.vpa.memory
Memory-related VPA settings.
- numberspec.resourcesManagement.vpa.memory.limitRatio
The memory limits/requests ratio.
If set, the limits are calculated based on the requests and the specified ratio.
- stringspec.resourcesManagement.vpa.memory.max
Maximum value of allowed memory requests to be submitted by the VPA.
Default:
2048Mi - stringspec.resourcesManagement.vpa.memory.min
Minimum value of allowed memory requests to be submitted by the VPA.
Default:
128Mi
- stringspec.resourcesManagement.vpa.mode
VPA operating mode.
Default:
InPlaceOrRecreateAllowed values:
Initial,InPlaceOrRecreate
- array of objectsspec.tolerations
Tolerations for waypoint proxy pods.
- stringspec.tolerations.effect
Allowed values:
NoSchedule,PreferNoSchedule,NoExecute - stringspec.tolerations.key
- stringspec.tolerations.operator
Default:
EqualAllowed values:
Exists,Equal - integerspec.tolerations.tolerationSeconds
- stringspec.tolerations.value
- stringspec.waypointFor
Controls the
istio.io/waypoint-forlabel on all managed resources.Default:
AllAllowed values:
All,Service,Workload
- objectstatus
- integerstatus.observedGeneration
Allowed values:
0 <= X - booleanstatus.synced
True when desired and actual resources are in sync.