Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 8 of 8 for moving (0.16 sec)

  1. manifests/charts/istiod-remote/templates/crd-all.gen.yaml

                          properties:
                            abort:
                              description: Abort Http request attempts and return error
                                codes back to downstream service, giving the impression
                                that the upstream service is faulty.
                              oneOf:
                              - not:
                                  anyOf:
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Apr 22 20:20:47 GMT 2024
    - 606.1K bytes
    - Viewed (0)
  2. manifests/charts/istio-control/istio-discovery/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.3K bytes
    - Viewed (0)
  3. manifests/charts/base/crds/crd-all.gen.yaml

                          properties:
                            abort:
                              description: Abort Http request attempts and return error
                                codes back to downstream service, giving the impression
                                that the upstream service is faulty.
                              oneOf:
                              - not:
                                  anyOf:
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Apr 22 20:20:47 GMT 2024
    - 606.1K bytes
    - Viewed (0)
  4. architecture/ambient/ztunnel.md

    Next, we terminate the CONNECT.
    From the [headers](#headers), we know the target destination.
    If the target destination has a waypoint, we enforce that the request is coming from that waypoint. Otherwise, the request is rejected.
    If there is no waypoint, ztunnel will enforce RBAC policies against the request.
    
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Thu Apr 25 22:35:16 GMT 2024
    - 16.6K bytes
    - Viewed (0)
  5. cni/pkg/iptables/iptables.go

    		"-j", "CONNMARK",
    		"--set-xmark", inpodTproxyMark)
    
    	// Handle healthcheck probes from the host node. In the host netns, before the packet enters the pod, we SNAT
    	// the healthcheck packet to a fixed IP if the packet is coming from a node-local process with a socket.
    	//
    	// We do this so we can exempt this traffic from ztunnel capture/proxy - otherwise both kube-proxy (legit)
    Go
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue May 07 19:54:50 GMT 2024
    - 19.7K bytes
    - Viewed (0)
  6. cni/pkg/util/podutil.go

    // otherwise fallback to 'PodIP'.
    //
    // Note that very early in the pod's lifecycle (before all the node CNI plugin invocations finish)
    // K8S may not have received the pod IPs yet, and may not report the pod as having any.
    func GetPodIPsIfPresent(pod *corev1.Pod) []netip.Addr {
    	var podIPs []netip.Addr
    	if len(pod.Status.PodIPs) != 0 {
    		for _, pip := range pod.Status.PodIPs {
    			ip := netip.MustParseAddr(pip.IP)
    Go
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Fri May 03 19:29:42 GMT 2024
    - 3.9K bytes
    - Viewed (0)
  7. 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)
  8. istioctl/pkg/describe/describe.go

    					if dr == nil {
    						// Don't bother giving the match conditions, the problem is that there are unknowns in the VirtualService
    						mismatchNotes = append(mismatchNotes, fmt.Sprintf("Warning: Route to subset %s but NO DESTINATION RULE defining subsets!", dest.Destination.Subset))
    					} else {
    						// Don't bother giving the match conditions, the problem is that there are unknowns in the VirtualService
    Go
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Sat Apr 13 05:23:38 GMT 2024
    - 50.4K bytes
    - Viewed (0)
Back to top