Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for models (0.3 sec)

  1. manifests/charts/istio-cni/values.yaml

          # UNSTABLE: If enabled, and ambient is enabled, enables ipv6 support
          ipv6: false
    
    
        repair:
          enabled: true
          hub: ""
          tag: ""
    
          # Repair controller has 3 modes. Pick which one meets your use cases. Note only one may be used.
          # This defines the action the controller will take when a pod is detected as broken.
    
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Apr 30 22:24:38 GMT 2024
    - 5.2K bytes
    - Viewed (1)
  2. manifests/charts/istiod-remote/values.yaml

        # Settings related to the untaint controller
        # This controller will remove `cni.istio.io/not-ready` from nodes when the istio-cni pod becomes ready
        # It should be noted that cluster operator/owner is responsible for having the taint set by their infrastructure provider when new nodes are added to the cluster; the untaint controller does not taint nodes
        taint:
          # Controls whether or not the untaint controller is active
          enabled: false
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Apr 22 22:00:40 GMT 2024
    - 20.2K bytes
    - Viewed (0)
  3. manifests/charts/gateways/istio-egress/values.yaml

          nodeSelector: {}
          tolerations: []
    
          # Specify the pod anti-affinity that allows you to constrain which nodes
          # your pod is eligible to be scheduled based on labels on pods that are
          # already running on the node rather than based on labels on nodes.
          # There are currently two types of anti-affinity:
          #    "requiredDuringSchedulingIgnoredDuringExecution"
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Feb 27 16:55:16 GMT 2024
    - 12.4K bytes
    - Viewed (0)
  4. manifests/charts/gateways/istio-ingress/values.yaml

          env: {}
          nodeSelector: {}
          tolerations: []
    
          # Specify the pod anti-affinity that allows you to constrain which nodes
          # your pod is eligible to be scheduled based on labels on pods that are
          # already running on the node rather than based on labels on nodes.
          # There are currently two types of anti-affinity:
          #    "requiredDuringSchedulingIgnoredDuringExecution"
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Feb 27 16:55:16 GMT 2024
    - 13K bytes
    - Viewed (0)
Back to top