Projects:Kubernetes: verschil tussen versies

Projects:Kubernetes (bekijk bron)

1.217 bytes toegevoegd , 10 mrt 2019

geen bewerkingssamenvatting

205

bewerkingen

@@ Regel 78: / Regel 78: @@
 * Weave is smart enough to figure out the most efficient way to use vxlan given your Linux kernel version.
 * It's also pretty simple: just a single Go binary.
+Kubernetes takes care that the pod network range and service network range is not only usable within pods, but also on the nodes. So, using the example values above, `https://10.96.0.1/` will reach the Kubernetes API server within pods and on nodes, also highly-available if you have multiple masters, which is pretty convenient.
+Some more important features of Kubernetes networking:
+* A Kubernetes cluster automatically runs a "CoreDNS" pod, which provides DNS to all other pods. It forwards requests outside the cluster to an upstream DNS server, but most importantly, provides an internal `cluster.local` DNS zone that you can use to look up other pods or services. For example, `kubernetes.default.svc.cluster.local` resolves to 10.96.0.1, as above. (In that hostname, 'kubernetes' is the service name, 'default' is the namespace.)
+* When a pod is listening on some TCP port, you don't need to use Services to reach them externally: <code>kubectl port-forward pod/foobarbaz 8080:80</code> forwards local port 8080 to port 80 of a pod called 'foobarbaz', and for this to work your <code>kubectl</code> can run on any machine with credentials to access the API server, it doesn't need to be part of the cluster.
 = Setting it all up =