dokucama

User Tools

Site Tools

Trace: • cicd • jinja2 • libvirt • kubernetes • linux_network_internals • netconf • raspberry
network_stuff:kubernetes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
network_stuff:kubernetes [2022/02/16 11:54] – jotasandokunetwork_stuff:kubernetes [2023/11/02 14:38] (current) – external edit 127.0.0.1
Line 13: Line 13:
   * [[https://blogs.cisco.com/cloud/service-mesh-for-network-engineers]]   * [[https://blogs.cisco.com/cloud/service-mesh-for-network-engineers]]
   * This is the [[https://kubernetes.io/docs/reference/glossary/?fundamental=true|GLOSSARY]]for kubernetes terms:   * This is the [[https://kubernetes.io/docs/reference/glossary/?fundamental=true|GLOSSARY]]for kubernetes terms:
 +  * **Cluster**: Consists of one master machine and multiple worker machines or nodes. The master coordinates between all the nodes
   * **Node**: just servers, connected to each other normally with (sdn) network   * **Node**: just servers, connected to each other normally with (sdn) network
     * the devops guy deploys a network overlay on the above ^ normally with a single 'kubectl' command (eg: vxlan overlay)     * the devops guy deploys a network overlay on the above ^ normally with a single 'kubectl' command (eg: vxlan overlay)
     * k8s install a 'kubelet' in each node to orchestrate it into clusters     * k8s install a 'kubelet' in each node to orchestrate it into clusters
     * kproxy: using iptables     * kproxy: using iptables
-  * **Cluster** +  * **Pod**: A pod runs a group of container that has common properties and can be orchestrated to scale up/down. (very coarse comparison is that the pod is like a "server" in the sense that groups related processes)
-    * Cluster consists of one master machine and multiple worker machines or nodes. The master coordinates between all the nodes +
-  * **Pod**: Ephemeral application/services. It appears after the 'deployment'. We can have the same Pod running in multiple containers.+
     * what stays static among the ephemeral pod states:     * what stays static among the ephemeral pod states:
       * service node port (nat)       * service node port (nat)
       * service cluster ip (internal, from pod to pod)       * service cluster ip (internal, from pod to pod)
       * service load balancer (external IP address, cluster exposed)       * service load balancer (external IP address, cluster exposed)
-    * **deployment > replicaSet > pod**+ 
 + 
 +\\ 
 + 
 +Deployment-object > replicaSet (that crates..) > pods\\ 
 +'service object/abstraction' k8s allows  for the pod to keep the same virtual IP in the microservice. : 
 +\\ 
 + 
 +A simple way of seeing this train is with: 
 +  ! in minikube 
 +  kubectl run mynode  # this creates a deployment object a replica set and pods 
 +  kubectl expose 
 +  
  
  
network_stuff/kubernetes.1645012478.txt.gz · Last modified: (external edit)

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki