- Sort Score
- Result 10 results
- Languages All
Results 1 - 6 of 6 for Blaser (0.16 sec)
-
architecture/ambient/ztunnel.md
* All traffic *ingressing* a pod on port 15008 in the mesh is assumed to be HBONE, and should be redirected to the node-local ztunnel on port 15008 (more on this later). * All other traffic *ingressing* a pod in the mesh should be redirected to the node-local ztunnel on port 15006, regardless of intended original destination port.
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) -
cni/pkg/nodeagent/net.go
// - this is because during add specifically, if CNI plugins have not finished executing, // K8S may get a pod Add event without any IPs in the object, and the pod will later be updated with IPs. // // We always need the IPs, but this is fine because this AddPodToMesh can be called from the CNI plugin as well,
Go - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 30 22:24:38 GMT 2024 - 12.2K bytes - Viewed (1) -
cni/pkg/nodeagent/server.go
if err != nil { return nil, fmt.Errorf("error configuring iptables: %w", err) } // Create hostprobe rules now, in the host netns // Later we will reuse this same configurator inside the pod netns for adding other rules iptablesConfigurator.DeleteHostRules()
Go - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 30 22:24:38 GMT 2024 - 7.2K bytes - Viewed (0) -
cni/pkg/nodeagent/informers.go
// or via the cni plugin. If it happens to get here before the cni plugin somehow, // then we will just fail to add the pod to the mesh, and it will be retried later when cni plugin adds it. // We need a pod IP - if the pod was added via the CNI plugin, that plugin told us the IPs // for the pod. If this is a pod added via informer, the pod should have already gone thru
Go - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri May 03 19:29:42 GMT 2024 - 9.6K bytes - Viewed (0) -
common/scripts/setup_env.sh
KUBECONFIG="${container_kubeconfig%?}" fi # LOCAL_OUT should point to architecture where we are currently running versus the desired. # This is used when we need to run a build artifact during tests or later as part of another # target. if [[ "${FOR_BUILD_CONTAINER:-0}" -eq "1" ]]; then # Override variables with container specific TARGET_OUT=${CONTAINER_TARGET_OUT} TARGET_OUT_LINUX=${CONTAINER_TARGET_OUT_LINUX}
Shell Script - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu May 02 16:31:40 GMT 2024 - 7.6K bytes - Viewed (0) -
istioctl/pkg/workload/workload.go
if err != nil { return nil, fmt.Errorf("configmap %s was not found in namespace %s: %v", istioCM, istioNamespace, err) } // fill some fields before applying the yaml to prevent errors later meshConfig := &meshconfig.MeshConfig{ DefaultConfig: &meshconfig.ProxyConfig{ ProxyMetadata: map[string]string{}, }, }
Go - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Apr 17 20:06:41 GMT 2024 - 25.5K bytes - Viewed (0)