Skip to content

Commit bdadfbc

Browse files
authored
Merge pull request #34489 from howieyuen/blog-slug-2016
[zh]fix 2016 blogs: add slug and remove url
2 parents 49ce07f + 4e766f7 commit bdadfbc

18 files changed

+33
-66
lines changed

content/zh-cn/blog/_posts/2016-01-00-Kubernetes-Community-Meeting-Notes.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,6 @@
22
title: " Kubernetes 社区会议记录 - 20160114 "
33
date: 2016-01-28
44
slug: kubernetes-community-meeting-notes
5-
url: /zh/blog/2016/01/Kubernetes-Community-Meeting-Notes
65
---
76
<!--
87
---

content/zh-cn/blog/_posts/2016-01-00-Simple-Leader-Election-With-Kubernetes.md

Lines changed: 7 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,20 @@
1-
<!--
21
---
3-
title: " Simple leader election with Kubernetes and Docker "
2+
title: "Kubernetes Docker 简单的 leader election"
43
date: 2016-01-11
54
slug: simple-leader-election-with-kubernetes
65
---
7-
8-
#### Overview
9-
-->
10-
11-
title: "Kubernetes 和 Docker 简单的 leader election"
6+
<!--
7+
title: " Simple leader election with Kubernetes and Docker "
128
date: 2016-01-11
139
slug: simple-leader-election-with-kubernetes
14-
url: /zh/blog/2016/01/Simple-Leader-Election-With-Kubernetes
10+
-->
1511

1612
<!--
13+
#### Overview
14+
1715
Kubernetes simplifies the deployment and operational management of services running on clusters. However, it also simplifies the development of these services. In this post we'll see how you can use Kubernetes to easily perform leader election in your distributed application. Distributed applications usually replicate the tasks of a service for reliability and scalability, but often it is necessary to designate one of the replicas as the leader who is responsible for coordination among all of the replicas.
1816
-->
17+
#### 概述
1918

2019
Kubernetes 简化了集群上运行的服务的部署和操作管理。但是,它也简化了这些服务的发展。在本文中,我们将看到如何使用 Kubernetes 在分布式应用程序中轻松地执行 leader election。分布式应用程序通常为了可靠性和可伸缩性而复制服务的任务,但通常需要指定其中一个副本作为负责所有副本之间协调的负责人。
2120

content/zh-cn/blog/_posts/2016-01-00-Why-Kubernetes-Doesnt-Use-Libnetwork.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,12 +4,12 @@ date: 2016-01-14
44
slug: why-kubernetes-doesnt-use-libnetwork
55
---
66

7-
<!-- ---
7+
<!--
88
title: " Why Kubernetes doesn’t use libnetwork "
99
date: 2016-01-14
1010
slug: why-kubernetes-doesnt-use-libnetwork
11-
url: /zh/blog/2016/01/Why-Kubernetes-Doesnt-Use-Libnetwork
12-
--- -->
11+
url: /blog/2016/01/Why-Kubernetes-Doesnt-Use-Libnetwork
12+
-->
1313

1414
<!-- 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? -->
1515

content/zh-cn/blog/_posts/2016-02-00-Kubecon-Eu-2016-Kubernetes-Community-In.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,10 @@ slug: kubecon-eu-2016-kubernetes-community-in
55
---
66

77
<!--
8-
---
98
title: " KubeCon EU 2016: Kubernetes Community in London "
109
date: 2016-02-24
1110
slug: kubecon-eu-2016-kubernetes-community-in
12-
url: /zh/blog/2016/02/Kubecon-Eu-2016-Kubernetes-Community-In
13-
---
11+
url: /blog/2016/02/Kubecon-Eu-2016-Kubernetes-Community-In
1412
-->
1513

1614
<!--

content/zh-cn/blog/_posts/2016-02-00-Kubernetes-Community-Meeting-Notes.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,9 @@ slug: kubernetes-community-meeting-notes
77
title: " Kubernetes community meeting notes - 20160204 "
88
date: 2016-02-09
99
slug: kubernetes-community-meeting-notes
10-
url: /zh/blog/2016/02/Kubernetes-Community-Meeting-Notes
10+
url: /blog/2016/02/Kubernetes-Community-Meeting-Notes
1111
-->
12+
1213
<!--
1314
#### February 4th - rkt demo (congratulations on the 1.0, CoreOS!), eBay puts k8s on Openstack and considers Openstack on k8s, SIGs, and flaky test surge makes progress.
1415
-->

content/zh-cn/blog/_posts/2016-02-00-State-Of-Container-World-January-2016.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,15 @@
11
---
2-
title: " 容器世界现状,2016年1月 "
2+
title: " 容器世界现状,2016 年 1 月 "
33
date: 2016-02-01
44
slug: state-of-container-world-january-2016
5-
url: /zh/blog/2016/02/State-Of-Container-World-January-2016
65
---
76
<!--
8-
---
97
title: " State of the Container World, January 2016 "
108
date: 2016-02-01
119
slug: state-of-container-world-january-2016
12-
url: /zh/blog/2016/02/State-Of-Container-World-January-2016
13-
---
10+
url: /blog/2016/02/State-Of-Container-World-January-2016
1411
-->
12+
1513
<!--
1614
At the start of the new year, we sent out a survey to gauge the state of the container world. We’re ready to send the [February edition](https://docs.google.com/forms/d/13yxxBqb5igUhwrrnDExLzZPjREiCnSs-AH-y4SSZ-5c/viewform), but before we do, let’s take a look at the January data from the 119 responses (thank you for participating!).
1715
-->

content/zh-cn/blog/_posts/2016-02-00-kubernetes-community-meeting-notes_23.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,14 @@
22
title: "Kubernetes 社区会议记录 - 20160218"
33
date: 2016-02-23
44
slug: kubernetes-community-meeting-notes_23
5-
url: /zh/blog/2016/02/kubernetes-community-meeting-notes_23
65
---
76

87
<!--
98
---
109
title: " Kubernetes Community Meeting Notes - 20160218 "
1110
date: 2016-02-23
1211
slug: kubernetes-community-meeting-notes_23
13-
url: /zh/blog/2016/02/kubernetes-community-meeting-notes_23
14-
url: /zh/blog/2016/02/kubernetes-community-meeting-notes_23
12+
url: /blog/2016/02/Kubernetes-community-meeting-notes-20160128
1513
---
1614
-->
1715

content/zh-cn/blog/_posts/2016-04-00-Adding-Support-For-Kubernetes-In-Rancher.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,12 @@
22
title: " 在 Rancher 中添加对 Kuernetes 的支持 "
33
date: 2016-04-08
44
slug: adding-support-for-kubernetes-in-rancher
5-
url: /zh/blog/2016/04/Adding-Support-For-Kubernetes-In-Rancher
65
---
76
<!--
8-
---
97
title: " Adding Support for Kubernetes in Rancher "
108
date: 2016-04-08
119
slug: adding-support-for-kubernetes-in-rancher
12-
url: /zh/blog/2016/04/Adding-Support-For-Kubernetes-In-Rancher
13-
---
10+
url: /blog/2016/04/Adding-Support-For-Kubernetes-In-Rancher
1411
-->
1512
<!--
1613
_Today’s guest post is written by Darren Shepherd, Chief Architect at Rancher Labs, an open-source software platform for managing containers._ -->

content/zh-cn/blog/_posts/2016-04-00-Kubernetes-Network-Policy-APIs.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,14 @@
22
title: “SIG-Networking:1.3 版本引入 Kubernetes 网络策略 API”
33
date: 2016-04-18
44
slug: kubernetes-network-policy-apis
5-
url: /zh/blog/2016/04/Kubernetes-Network-Policy-APIs
65
---
76
<!--
8-
---
97
title: " SIG-Networking: Kubernetes Network Policy APIs Coming in 1.3 "
108
date: 2016-04-18
119
slug: kubernetes-network-policy-apis
12-
url: /zh/blog/2016/04/Kubernetes-Network-Policy-APIs
13-
---
10+
url: /blog/2016/04/Kubernetes-Network-Policy-APIs
1411
-->
12+
1513
<!--
1614
_Editor’s note: This week we’re featuring [Kubernetes Special Interest Groups](https://github.com/kubernetes/kubernetes/wiki/Special-Interest-Groups-(SIGs)); Today’s post is by the Network-SIG team describing network policy APIs coming in 1.3 - policies for security, isolation and multi-tenancy._
1715
-->

content/zh-cn/blog/_posts/2016-04-00-Sig-Clusterops-Promote-Operability-And-Interoperability-Of-K8S-Clusters.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,14 @@
22
title: " SIG-ClusterOps: 提升 Kubernetes 集群的可操作性和互操作性 "
33
date: 2016-04-19
44
slug: sig-clusterops-promote-operability-and-interoperability-of-k8s-clusters
5-
url: /zh/blog/2016/04/Sig-Clusterops-Promote-Operability-And-Interoperability-Of-K8S-Clusters
65
---
76
<!--
8-
---
97
title: " SIG-ClusterOps: Promote operability and interoperability of Kubernetes clusters "
108
date: 2016-04-19
119
slug: sig-clusterops-promote-operability-and-interoperability-of-k8s-clusters
12-
url: /zh/blog/2016/04/Sig-Clusterops-Promote-Operability-And-Interoperability-Of-K8S-Clusters
13-
---
10+
url: /blog/2016/04/Sig-Clusterops-Promote-Operability-And-Interoperability-Of-K8S-Clusters
1411
-->
12+
1513
<!--
1614
_Editor’s note: This week we’re featuring [Kubernetes Special Interest Groups](https://github.com/kubernetes/kubernetes/wiki/Special-Interest-Groups-(SIGs)); Today’s post is by the SIG-ClusterOps team whose mission is to promote operability and interoperability of Kubernetes clusters -- to listen, help & escalate._
1715
-->

0 commit comments

Comments
 (0)