whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix blog articles using wrong custom URIs

Browse Source 
Some blog articles with custom URIs have been localized into Chinese
without removing the custom URI from the front matter.

Update these articles to use appropriate URIs.
This commit is contained in:
Tim Bannister
2022-03-02 16:24:18 +00:00
parent a9f7219210
commit 5c970ca1b0
37 changed files with 52 additions and 52 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/zh/blog/_posts/2016-01-00-Why-Kubernetes-Doesnt-Use-Libnetwork.md
+1 -1
View File
@@ -8,7 +8,7 @@ slug: why-kubernetes-doesnt-use-libnetwork
title: " Why Kubernetes doesn’t use libnetwork "
date: 2016-01-14
slug: why-kubernetes-doesnt-use-libnetwork
url: /blog/2016/01/Why-Kubernetes-Doesnt-Use-Libnetwork
url: /zh/blog/2016/01/Why-Kubernetes-Doesnt-Use-Libnetwork
--- -->
<!-- Kubernetes has had a very basic form of network plugins since before version 1.0 was released — around the same time as Docker's [libnetwork](https://github.com/docker/libnetwork) and Container Network Model ([CNM](https://github.com/docker/libnetwork/blob/master/docs/design.md)) was introduced. Unlike libnetwork, the Kubernetes plugin system still retains its "alpha" designation. Now that Docker's network plugin support is released and supported, an obvious question we get is why Kubernetes has not adopted it yet. After all, vendors will almost certainly be writing plugins for Docker — we would all be better off using the same drivers, right? -->