github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-29 14:37:00 +00:00
Code Issues Projects Releases Wiki Activity

fix style of yaml and text

Browse Source
This commit is contained in:
zhangxiaoyu-zidif 2017-07-02 12:11:33 +08:00
parent 5eccc7ae80
commit 5fa4668e9f
1 changed files with 70 additions and 62 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

132
CHANGELOG.md
View File

@ -2000,37 +2000,41 @@ filename | sha256 hash
* Support updating storageclasses in etcd to storage.k8s.io/v1. You must do this prior to upgrading to 1.8. ([#46116](https://github.com/kubernetes/kubernetes/pull/46116), [@ncdc](https://github.com/ncdc)) * Support updating storageclasses in etcd to storage.k8s.io/v1. You must do this prior to upgrading to 1.8. ([#46116](https://github.com/kubernetes/kubernetes/pull/46116), [@ncdc](https://github.com/ncdc))
* The namespace API object no longer supports the deletecollection operation. ([#46407](https://github.com/kubernetes/kubernetes/pull/46407), [@liggitt](https://github.com/liggitt)) * The namespace API object no longer supports the deletecollection operation. ([#46407](https://github.com/kubernetes/kubernetes/pull/46407), [@liggitt](https://github.com/liggitt))
* NetworkPolicy has been moved from `extensions/v1beta1` to the new ([#39164](https://github.com/kubernetes/kubernetes/pull/39164), [@danwinship](https://github.com/danwinship)) * NetworkPolicy has been moved from `extensions/v1beta1` to the new ([#39164](https://github.com/kubernetes/kubernetes/pull/39164), [@danwinship](https://github.com/danwinship))
* `networking.k8s.io/v1` API group. The structure remains unchanged from `networking.k8s.io/v1` API group. The structure remains unchanged from
* the beta1 API. the beta1 API.
* The `net.beta.kubernetes.io/network-policy` annotation on Namespaces The `net.beta.kubernetes.io/network-policy` annotation on Namespaces
* to opt in to isolation has been removed. Instead, isolation is now to opt in to isolation has been removed. Instead, isolation is now
* determined at a per-pod level, with pods being isolated if there is determined at a per-pod level, with pods being isolated if there is
* any NetworkPolicy whose spec.podSelector targets them. Pods that are any NetworkPolicy whose spec.podSelector targets them. Pods that are
* targeted by NetworkPolicies accept traffic that is accepted by any of targeted by NetworkPolicies accept traffic that is accepted by any of
* the NetworkPolicies (and nothing else), and pods that are not targeted the NetworkPolicies (and nothing else), and pods that are not targeted
* by any NetworkPolicy accept all traffic by default. by any NetworkPolicy accept all traffic by default.
* Action Required: Action Required:
* When upgrading to Kubernetes 1.7 (and a network plugin that supports When upgrading to Kubernetes 1.7 (and a network plugin that supports
* the new NetworkPolicy v1 semantics), to ensure full behavioral the new NetworkPolicy v1 semantics), to ensure full behavioral
* compatibility with v1beta1: compatibility with v1beta1:
* 1. In Namespaces that previously had the "DefaultDeny" annotation, 1. In Namespaces that previously had the "DefaultDeny" annotation,
* you can create equivalent v1 semantics by creating a you can create equivalent v1 semantics by creating a
* NetworkPolicy that matches all pods but does not allow any NetworkPolicy that matches all pods but does not allow any
* traffic: traffic:
* kind: NetworkPolicy
* apiVersion: networking.k8s.io/v1 ```yaml
* metadata: kind: NetworkPolicy
* name: default-deny apiVersion: networking.k8s.io/v1
* spec: metadata:
* podSelector: name: default-deny
* This will ensure that pods that aren't matched by any other spec:
* NetworkPolicy will continue to be fully-isolated, as they were podSelector:
* before. ```
* 2. In Namespaces that previously did not have the "DefaultDeny"
* annotation, you should delete any existing NetworkPolicy This will ensure that pods that aren't matched by any other
* objects. These would have had no effect before, but with v1 NetworkPolicy will continue to be fully-isolated, as they were
* semantics they might cause some traffic to be blocked that you before.
* didn't intend to be blocked. 2. In Namespaces that previously did not have the "DefaultDeny"
annotation, you should delete any existing NetworkPolicy
objects. These would have had no effect before, but with v1
semantics they might cause some traffic to be blocked that you
didn't intend to be blocked.
### Other notable changes ### Other notable changes
@ -2493,37 +2497,41 @@ filename | sha256 hash
* Support updating storageclasses in etcd to storage.k8s.io/v1. You must do this prior to upgrading to 1.8. ([#46116](https://github.com/kubernetes/kubernetes/pull/46116), [@ncdc](https://github.com/ncdc)) * Support updating storageclasses in etcd to storage.k8s.io/v1. You must do this prior to upgrading to 1.8. ([#46116](https://github.com/kubernetes/kubernetes/pull/46116), [@ncdc](https://github.com/ncdc))
* The namespace API object no longer supports the deletecollection operation. ([#46407](https://github.com/kubernetes/kubernetes/pull/46407), [@liggitt](https://github.com/liggitt)) * The namespace API object no longer supports the deletecollection operation. ([#46407](https://github.com/kubernetes/kubernetes/pull/46407), [@liggitt](https://github.com/liggitt))
* NetworkPolicy has been moved from `extensions/v1beta1` to the new ([#39164](https://github.com/kubernetes/kubernetes/pull/39164), [@danwinship](https://github.com/danwinship)) * NetworkPolicy has been moved from `extensions/v1beta1` to the new ([#39164](https://github.com/kubernetes/kubernetes/pull/39164), [@danwinship](https://github.com/danwinship))
* `networking.k8s.io/v1` API group. The structure remains unchanged from `networking.k8s.io/v1` API group. The structure remains unchanged from
* the beta1 API. the beta1 API.
* The `net.beta.kubernetes.io/network-policy` annotation on Namespaces The `net.beta.kubernetes.io/network-policy` annotation on Namespaces
* to opt in to isolation has been removed. Instead, isolation is now to opt in to isolation has been removed. Instead, isolation is now
* determined at a per-pod level, with pods being isolated if there is determined at a per-pod level, with pods being isolated if there is
* any NetworkPolicy whose spec.podSelector targets them. Pods that are any NetworkPolicy whose spec.podSelector targets them. Pods that are
* targeted by NetworkPolicies accept traffic that is accepted by any of targeted by NetworkPolicies accept traffic that is accepted by any of
* the NetworkPolicies (and nothing else), and pods that are not targeted the NetworkPolicies (and nothing else), and pods that are not targeted
* by any NetworkPolicy accept all traffic by default. by any NetworkPolicy accept all traffic by default.
* Action Required: Action Required:
* When upgrading to Kubernetes 1.7 (and a network plugin that supports When upgrading to Kubernetes 1.7 (and a network plugin that supports
* the new NetworkPolicy v1 semantics), to ensure full behavioral the new NetworkPolicy v1 semantics), to ensure full behavioral
* compatibility with v1beta1: compatibility with v1beta1:
* 1. In Namespaces that previously had the "DefaultDeny" annotation, 1. In Namespaces that previously had the "DefaultDeny" annotation,
* you can create equivalent v1 semantics by creating a you can create equivalent v1 semantics by creating a
* NetworkPolicy that matches all pods but does not allow any NetworkPolicy that matches all pods but does not allow any
* traffic: traffic:
* kind: NetworkPolicy
* apiVersion: networking.k8s.io/v1 ```yaml
* metadata: kind: NetworkPolicy
* name: default-deny apiVersion: networking.k8s.io/v1
* spec: metadata:
* podSelector: name: default-deny
* This will ensure that pods that aren't matched by any other spec:
* NetworkPolicy will continue to be fully-isolated, as they were podSelector:
* before. ```
* 2. In Namespaces that previously did not have the "DefaultDeny"
* annotation, you should delete any existing NetworkPolicy This will ensure that pods that aren't matched by any other
* objects. These would have had no effect before, but with v1 NetworkPolicy will continue to be fully-isolated, as they were
* semantics they might cause some traffic to be blocked that you before.
* didn't intend to be blocked. 2. In Namespaces that previously did not have the "DefaultDeny"
annotation, you should delete any existing NetworkPolicy
objects. These would have had no effect before, but with v1
semantics they might cause some traffic to be blocked that you
didn't intend to be blocked.
### Other notable changes ### Other notable changes