- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 332 for vips (0.07 sec)
-
cmd/kubeadm/app/cmd/options/constant.go
// NetworkingDNSDomain flag sets the domain for services, e.g. "myorg.internal". NetworkingDNSDomain = "service-dns-domain" // NetworkingServiceSubnet flag sets the range of IP address for service VIPs. NetworkingServiceSubnet = "service-cidr" // NetworkingPodSubnet flag sets the range of IP addresses for the pod network. If set, the control plane will automatically allocate CIDRs for every node.
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Thu Feb 29 05:14:21 UTC 2024 - 6.9K bytes - Viewed (0) -
pilot/pkg/xds/xds_test.go
ConfigString: ` apiVersion: networking.istio.io/v1alpha3 kind: ServiceEntry metadata: name: external-svc-mongocluster spec: hosts: - mymongodb.somedomain addresses: - 192.192.192.192/24 # VIPs ports: - number: 27018 name: mongodb protocol: MONGO location: MESH_INTERNAL resolution: STATIC endpoints: - address: 2.2.2.2 - address: 3.3.3.3 `, },
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Wed Mar 27 16:59:05 UTC 2024 - 13.8K bytes - Viewed (0) -
pkg/dns/server/name_table_test.go
Ips: []string{"1.2.3.4"}, Registry: "Kubernetes", Shortname: "pod1.headless-svc", Namespace: "testns", }, "pod3.headless-svc.testns.svc.cluster.local": { Ips: []string{"19.6.7.8"}, Registry: "Kubernetes", Shortname: "pod3.headless-svc", Namespace: "testns", }, "pod4.headless-svc.testns.svc.cluster.local": {
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Thu Jan 25 04:26:03 UTC 2024 - 16K bytes - Viewed (0) -
pilot/pkg/networking/core/tls.go
// 2) or if we have an empty destination VIP (i.e. which we should never get in case some platform adapter improper handlings); // 3) or if the destination is a wildcard destination VIP with the listener bound to the wildcard as well. // In the above cited cases, the listener will be bound to 0.0.0.0. So SNI match is the only way to distinguish different
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Thu Mar 28 17:09:02 UTC 2024 - 14.7K bytes - Viewed (0) -
tests/integration/pilot/mcs/discoverability/discoverability_test.go
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Mon Apr 08 22:02:59 UTC 2024 - 17.9K bytes - Viewed (0) -
pilot/pkg/serviceregistry/aggregate/controller.go
services[previous] = services[previous].DeepCopy() } // If it is seen second time, that means it is from a different cluster, update cluster VIPs. mergeService(services[previous], s, r) } } } } return services } // GetService retrieves a service by hostname if exists
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Wed May 15 06:28:11 UTC 2024 - 13.5K bytes - Viewed (0) -
pilot/pkg/model/service.go
// hostnames. The IPs assigned to services are not // synchronized across istiod replicas as the DNS resolution // for these service entries happens completely inside a pod // whose proxy is managed by one istiod. That said, the algorithm // to allocate IPs is pretty deterministic that at stable state, two // istiods will allocate the exact same set of IPs for a given set of // service entries.
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Wed May 29 02:03:58 UTC 2024 - 46.3K bytes - Viewed (0) -
pilot/pkg/networking/core/listener_waypoint.go
func (lb *ListenerBuilder) buildWaypointInbound() []*listener.Listener { listeners := []*listener.Listener{} // We create 3 listeners: // 1. Decapsulation CONNECT listener. // 2. IP dispatch listener, handling both VIPs and direct pod IPs. // 3. Encapsulation CONNECT listener, originating the tunnel wls, wps := findWaypointResources(lb.node, lb.push) listeners = append(listeners, lb.buildWaypointInboundConnectTerminate(),
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Fri Jun 14 04:34:37 UTC 2024 - 27.6K bytes - Viewed (0) -
cmd/kubeadm/app/cmd/init.go
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Wed Jan 17 03:37:05 UTC 2024 - 24.1K bytes - Viewed (0) -
pkg/proxy/ipvs/proxier.go
// The kube dummy interface has all service VIPs assigned which // results in the service VIP being picked as the source IP to reach // a VIP. This leads to a connection from VIP:<random port> to // VIP:<service port>. // Always masquerading OUTPUT (node-originating) traffic with a VIP // source ip and service port destination fixes the outgoing connections.
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Sun Apr 28 15:51:23 UTC 2024 - 77.7K bytes - Viewed (0)