diff options
| author | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-02-20 15:26:39 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-02-20 15:26:39 -0800 |
| commit | d34cd9b58f97bcf18babea32b2bbb53f7d0e17d7 (patch) | |
| tree | 04e9034fe07270d71ff0d8837ea248ca394e21b5 | |
| parent | 8dd1cb5a9ae64fac6d9d6cb9c749c9a3200b1290 (diff) | |
| parent | a1ce92493d9f0c51be8db9b1b78edb5b32d620a1 (diff) | |
Merge pull request #1825 from cblecker/whitespace-fox
Fix whitespace for sig-multicluster
| -rw-r--r-- | sig-multicluster/README.md | 2 | ||||
| -rw-r--r-- | sigs.yaml | 18 |
2 files changed, 10 insertions, 10 deletions
diff --git a/sig-multicluster/README.md b/sig-multicluster/README.md index fd648b9a..6bd6f692 100644 --- a/sig-multicluster/README.md +++ b/sig-multicluster/README.md @@ -8,7 +8,7 @@ To understand how this file is generated, see https://git.k8s.io/community/gener --> # Multicluster SIG -A Special Interest Group focussed on solving common challenges related to the management of multiple Kubernetes clusters, and applications that exist therein. The SIG will be responsible for designing, discussing, implementing and maintaining API’s, tools and documentation related to multi-cluster administration and application management. This includes not only active automated approaches such as Cluster Federation, but also those that employ batch workflow-style continuous deployment systems like Spinnaker and others. Standalone building blocks for these and other similar systems (for example a cluster registry), and proposed changes to kubernetes core where appropriate will also be in scope. +A Special Interest Group focussed on solving common challenges related to the management of multiple Kubernetes clusters, and applications that exist therein. The SIG will be responsible for designing, discussing, implementing and maintaining API’s, tools and documentation related to multi-cluster administration and application management. This includes not only active automated approaches such as Cluster Federation, but also those that employ batch workflow-style continuous deployment systems like Spinnaker and others. Standalone building blocks for these and other similar systems (for example a cluster registry), and proposed changes to kubernetes core where appropriate will also be in scope. ## Meetings * Regular SIG Meeting: [Tuesdays at 9:30 PT (Pacific Time)](https://zoom.us/my/k8s.mc) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=9:30&tz=PT%20%28Pacific%20Time%29). @@ -183,7 +183,7 @@ sigs: - https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/controller/history/OWNERS - https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/controller/job/OWNERS - https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/controller/replicaset/OWNERS - - https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/controller/statefulset/OWNERS + - https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/controller/statefulset/OWNERS - https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/apis/apps/OWNERS - https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/apis/batch/OWNERS - https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/registry/apps/OWNERS @@ -826,14 +826,14 @@ sigs: - name: Multicluster dir: sig-multicluster mission_statement: > - A Special Interest Group focussed on solving common challenges related to the + A Special Interest Group focussed on solving common challenges related to the management of multiple Kubernetes clusters, and applications that exist therein. - The SIG will be responsible for designing, discussing, implementing and maintaining - API’s, tools and documentation related to multi-cluster administration and application - management. This includes not only active automated approaches such as Cluster - Federation, but also those that employ batch workflow-style continuous deployment - systems like Spinnaker and others. Standalone building blocks for these and other - similar systems (for example a cluster registry), and proposed changes to kubernetes + The SIG will be responsible for designing, discussing, implementing and maintaining + API’s, tools and documentation related to multi-cluster administration and application + management. This includes not only active automated approaches such as Cluster + Federation, but also those that employ batch workflow-style continuous deployment + systems like Spinnaker and others. Standalone building blocks for these and other + similar systems (for example a cluster registry), and proposed changes to kubernetes core where appropriate will also be in scope. label: multicluster leads: @@ -1457,7 +1457,7 @@ sigs: - name: testing-commons description: "The Testing Commons is a subproject within the Kubernetes sig-testing community interested code structure, layout, and execution of common test code used throughout the kubernetes project." owners: - - https://raw.githubusercontent.com/kubernetes-sig-testing/frameworks/master/OWNERS + - https://raw.githubusercontent.com/kubernetes-sig-testing/frameworks/master/OWNERS - https://raw.githubusercontent.com/kubernetes/kubernetes/master/test/OWNERS meetings: - description: Testing Commons |