You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/blog/_posts/2024-04-05-diy-create-your-own-cloud-with-kubernetes-part-2/index.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ In case you are using Talos Linux, as we described in the [previous article](/bl
81
81
82
82
## Networking for Kubernetes VMs
83
83
84
-
Despite having the similar interface - CNI, The network architecture in Kubernetes is actually more complex and typically consists of many independent components that are not directly connected to each other. In fact you can split Kubernetes networking into four layers, which are described below.
84
+
Despite having the similar interface - CNI, The network architecture in Kubernetes is actually more complex and typically consists of many independent components that are not directly connected to each other. In fact, you can split Kubernetes networking into four layers, which are described below.
85
85
86
86
### Node Network (Data Center Network)
87
87
@@ -110,7 +110,7 @@ In Kube-OVN you can assign separate subnets to an entire namespace or connect th
110
110
### Services Network
111
111
112
112
In addition to the CNI plugin, Kubernetes also has a services network, which is primarily needed for service discovery.
113
-
Contrary to traditional virtual machines, Kubernetes originally designed to run pods with a random address.
113
+
Contrary to traditional virtual machines, Kubernetes is originally designed to run pods with a random address.
114
114
And the services network provides a convenient abstraction (stable IP addresses and DNS names) that will always direct traffic to the correct pod.
115
115
The same approach is also commonly used with virtual machines in clouds despite the fact that their IPs are usually static.
116
116
@@ -122,7 +122,7 @@ But nowadays, this functionality might be provided as part of the CNI plugin. Th
122
122
123
123
Cilium is based on the eBPF technology, which allows for efficient offloading of the Linux networking stack, thereby improving performance and security compared to traditional methods based on iptables.
124
124
125
-
In practice, Cilium and Kube-OVN can be easily [integrated](https://kube-ovn.readthedocs.io/zh-cn/stable/en/advance/with-cilium/) to provide a unified solution that offers seamless multi-tenant networking for virtual machines, as well as advanced network policies and combined services network functionality.
125
+
In practice, Cilium and Kube-OVN can be easily [integrated](https://kube-ovn.readthedocs.io/zh-cn/stable/en/advance/with-cilium/) to provide a unified solution that offers seamless, multi-tenant networking for virtual machines, as well as advanced network policies and combined services network functionality.
126
126
127
127
### External Traffic Load Balancer
128
128
@@ -140,11 +140,11 @@ In most cases, setting up a load balancer on bare metal is achieved by creating
140
140
141
141
After exploring various options, we decided that MetalLB is the simplest and most reliable solution, although we do not strictly enforce the use of only it.
142
142
143
-
Another benefit is that in L2 mode, MetalLB speakers continuously checking thir neighbors state by sending preforming liveness checks using a memberlist protocol.
143
+
Another benefit is that in L2 mode, MetalLB speakers continuously check their neighbour's state by sending preforming liveness checks using a memberlist protocol.
144
144
This enables failover that works independently of Kubernetes control-plane.
145
145
146
146
## Conclusion
147
147
148
148
This concludes our overview of virtualization, storage, and networking in Kubernetes. The technologies mentioned here are available and already pre-configured on the [Cozystack](https://github.com/aenix-io/cozystack) platform, where you can try them with no limitations.
149
149
150
-
In the [next article](/blog/2024/04/05/diy-create-your-own-cloud-with-kubernetes-part-3/), we will detail how, on top of this, we implement the provisioning of fully functional Kubernetes clusters with just the push of a button.
150
+
In the [next article](/blog/2024/04/05/diy-create-your-own-cloud-with-kubernetes-part-3/), I'll detail how, on top of this, you can implement the provisioning of fully functional Kubernetes clusters with just the click of a button.
0 commit comments