Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 5 of 5 for becomes (0.19 sec)

  1. manifests/charts/istio-control/istio-discovery/values.yaml

        extraContainerArgs: []
    
        env: {}
        
        # 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:
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Apr 22 22:00:40 GMT 2024
    - 20.3K bytes
    - Viewed (0)
  2. manifests/charts/istiod-remote/values.yaml

        # Additional container arguments
        extraContainerArgs: []
        env: {}
        # 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:
    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/istio-cni/values.yaml

          deletePods: false
          # repairPods will dynamically repair any broken pod by setting up the pod networking configuration even after it has started.
          # Note the pod will be crashlooping, so this may take a few minutes to become fully functional based on when the retry occurs.
          # This requires no RBAC privilege, but does require `securityContext.privileged/CAP_SYS_ADMIN`.
          repairPods: true
    
          initContainerName: "istio-validation"
    
    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)
  4. manifests/charts/gateways/istio-egress/values.yaml

        # - Meshes will be federated together
        # - Policy will be written referencing one mesh from the other
        #
        # If an administrator expects that any of these conditions may become true in
        # the future, they should ensure their meshes have different Mesh IDs
        # assigned.
        #
        # Within a multicluster mesh, each cluster must be (manually or auto)
    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)
  5. manifests/charts/gateways/istio-ingress/values.yaml

        # - Meshes will be federated together
        # - Policy will be written referencing one mesh from the other
        #
        # If an administrator expects that any of these conditions may become true in
        # the future, they should ensure their meshes have different Mesh IDs
        # assigned.
        #
        # Within a multicluster mesh, each cluster must be (manually or auto)
    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