github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
50,984 Commits
32 Branches
881 Tags
633 MiB
Commit Graph

371 Commits (a2f2e1d4918effb4f0994333c7b88086674e4a5b)

Author SHA1 Message Date
Christoph Blecker ac86803a74
Remove docs/ other than auto generated 2017-06-01 23:10:47 -07:00
Michelle Noorali dd639c6376 replace contents of docs/design with stubs 2017-01-11 08:23:44 -05:00
Kubernetes Submit Queue 7a57e80ef6 Merge pull request #37478 from YuPengZTE/devMD037 
Automatic merge from submit-queue

fix the mistake type

<!--  Thanks for sending a pull request!  Here are some tips for you:
1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md
2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md
3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes
-->

**What this PR does / why we need it**:

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #

**Special notes for your reviewer**:

**Release note**:
<!--  Steps to write your release note:
1. Use the release-note-* labels to set the release note state (if you have access) 
2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. 
-->
```release-note
```

Signed-off-by: yupeng <yu.peng36@zte.com.cn>
 2016-11-28 11:45:09 -08:00
Kubernetes Submit Queue 7ee7cf5ccc Merge pull request #34315 from seeekr/patch-1 
Automatic merge from submit-queue

fix typo in podaffinity.md
 2016-11-28 11:44:22 -08:00
Kubernetes Submit Queue 626918aa4f Merge pull request #37120 from thockin/scary-warning-again 
Automatic merge from submit-queue

Remove a few versioned-warnings that snuck in, again
 2016-11-28 11:43:54 -08:00
Kubernetes Submit Queue 29c013ae8d Merge pull request #36975 from xiangpengzhao/fix-design-doc 
Automatic merge from submit-queue

Fix container to pod in resource-qos.md

`...then the container is classified as Guaranteed.`
Here `container` should be `pod`.
 2016-11-28 11:43:26 -08:00
yupeng bee751eead fix the mistake type 
Signed-off-by: yupeng <yu.peng36@zte.com.cn>
 2016-11-25 17:34:31 +08:00
Tim Hockin 0772c9b6f9 Remove a few versioned-warnings that snuck in, again 2016-11-18 13:28:46 -08:00
xiangpengzhao 94f5f25589 Fix container to pod in resource-qos.md 2016-11-17 00:08:13 -05:00
Jeff Vance aa87fbec47 added details on pv-pvc matching 2016-11-15 20:16:34 -08:00
Jimmy Cuadra d42eabd9d2 Rename PetSet to StatefulSet in docs and examples. 2016-11-05 00:17:28 -07:00
Kubernetes Submit Queue 4b3d6b4bde Merge pull request #36123 from guangxuli/k8s_add_new_secret_type 
Automatic merge from submit-queue

add latest docker config secret type
 2016-11-04 08:54:09 -07:00
Kubernetes Submit Queue 4280eed6b2 Merge pull request #29649 from fgrzadkowski/ha_design_doc 
Automatic merge from submit-queue

Design for automated HA master deployment

https://github.com/kubernetes/kubernetes/issues/21124

@jszczepkowski @davidopp @roberthbailey @xiang90 @mikedanese
 2016-11-04 01:17:01 -07:00
guangxuli ecc44d63cd add latest docker config secret type 2016-11-03 09:40:34 +08:00
Sergey Maslyakov 61554f08bd Editorial: An orphaned "which" deleted. 2016-10-31 10:59:36 -05:00
Filip Grzadkowski 2e5f27d940 Design for automated HA master deployment 2016-10-28 12:16:05 +02:00
Tim Hockin b0fa2056a6 Remove 'this is HEAD' warning on docs 2016-10-26 00:06:59 +02:00
Kubernetes Submit Queue 081ee2d5ad Merge pull request #34090 from mwielgus/designdoc-rs 
Automatic merge from submit-queue

Federated replica set design doc

cc: @quinton-hoole @kubernetes/sig-cluster-federation
 2016-10-22 14:55:29 -07:00
Marcin Wielgus c44897f97d Federated replica set design doc 2016-10-22 23:05:35 +02:00
Kubernetes Submit Queue 07b777fee1 Merge pull request #34758 from fgrzadkowski/monitoring_arch 
Automatic merge from submit-queue

Add monitoring architecture

<!--  Thanks for sending a pull request!  Here are some tips for you:
1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md
2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md
3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes
-->

**What this PR does / why we need it**: This adds a description of monitoring architecture.

**Special notes for your reviewer**: This proposal have been already extensively discussed in [this doc](https://docs.google.com/document/d/1z7R44MUz_5gRLwsVH0S9rOy8W5naM9XE5NrbeGIqO2k); this is just a copy&paste so that it's in our repo.

@kubernetes/autoscaling @kubernetes/sig-instrumentation @DirectXMan12 @davidopp @piosz @derekwaynecarr @thockin 

**Release note**:
<!--  Steps to write your release note:
1. Use the release-note-* labels to set the release note state (if you have access) 
2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. 
-->
```release-note
NONE
```
 2016-10-17 07:43:23 -07:00
Filip Grzadkowski d021c230fe Add monitoring architecture. 2016-10-17 15:21:49 +02:00
Kubernetes Submit Queue 1a90b4b72c Merge pull request #31368 from vladi-dev/master 
Automatic merge from submit-queue

Doc: Explain how to use EBS storage on AWS

<!--  Thanks for sending a pull request!  Here are some tips for you:
1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md
2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md
3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes
-->

**What this PR does / why we need it**:

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #

**Special notes for your reviewer**:

**Release note**:
<!--  Steps to write your release note:
1. Use the release-note-* labels to set the release note state (if you have access) 
2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. 
-->
```release-note
```
 2016-10-15 12:17:20 -07:00
Kubernetes Submit Queue 27dcf27ad8 Merge pull request #33076 from YuPengZTE/devIE 
Automatic merge from submit-queue

ie. should be i.e.
 2016-10-15 08:50:02 -07:00
Kubernetes Submit Queue a0d4878ea9 Merge pull request #30145 from markturansky/limit_range_pvc 
Automatic merge from submit-queue

Add PVC storage to LimitRange

This PR adds the ability to add a LimitRange to a namespace that enforces min/max on `pvc.Spec.Resources.Requests["storage"]`.

@derekwaynecarr @abhgupta @kubernetes/sig-storage 

Examples forthcoming. 

```release-note
pvc.Spec.Resources.Requests min and max can be enforced with a LimitRange of type "PersistentVolumeClaim" in the namespace
```
 2016-10-12 20:26:59 -07:00
Denis Andrejew 4d9286eb83 fix typo in podaffinity.md 2016-10-07 12:48:02 +02:00
markturansky 0d40104c1d add pvc storage to LimitRange 2016-10-05 17:31:15 -04:00
Joe Beda 17454a04ac Remove support for boot2docker 2016-10-03 19:42:20 -07:00
Kubernetes Submit Queue 7dcae5edd8 Merge pull request #25260 from duglin/minion 
Automatic merge from submit-queue

Change minion to node

Continuation of #1111

I tried to keep this PR down to just a simple search-n-replace to keep
things simple.  I may have gone too far in some spots but its easy to
roll those back if needed - just let me know.

I avoided renaming `contrib/mesos/pkg/minion` because there's already
a `contrib/mesos/pkg/node` dir and fixing that will require a bit of work
due to a circular import chain that pops up. So I'm saving that for a
follow-on PR.

Signed-off-by: Doug Davis <dug@us.ibm.com>
 2016-09-28 20:08:59 -07:00
Dan Williams f1aaf79fb4 docs/networking: update IPv6 support section 2016-09-28 16:58:55 -05:00
Doug Davis 9d5bac6330 Change minion to node 
Contination of #1111

I tried to keep this PR down to just a simple search-n-replace to keep
things simple.  I may have gone too far in some spots but its easy to
roll those back if needed.

I avoided renaming `contrib/mesos/pkg/minion` because there's already
a `contrib/mesos/pkg/node` dir and fixing that will require a bit of work
due to a circular import chain that pops up. So I'm saving that for a
follow-on PR.

I rolled back some of this from a previous commit because it just got
to big/messy. Will follow up with additional PRs

Signed-off-by: Doug Davis <dug@us.ibm.com>
 2016-09-28 10:53:30 -07:00
Paul Morie 3335a5bb19 Move SELinux proposal to docs/design 2016-09-27 13:00:59 -04:00
Kubernetes Submit Queue 45723e0778 Merge pull request #33471 from YuPengZTE/devVS 
Automatic merge from submit-queue

The VS and dot is seprated
 2016-09-27 07:32:16 -07:00
Kubernetes Submit Queue 4339b87ae3 Merge pull request #31228 from yuexiao-wang/fix-makefile 
Automatic merge from submit-queue

Add targets for PHONY in Makefile

Add targets for PHONY in Makefile and keep the same style between rules and PHONY

Signed-off-by: yuexiao-wang <wang.yuexiao@zte.com.cn>
 2016-09-26 22:30:10 -07:00
YuPengZTE d0f69ee0f9 The VS and dot is seprated 
Signed-off-by: YuPengZTE <yu.peng36@zte.com.cn>
 2016-09-26 17:05:53 +08:00
YuPengZTE f3a000757c ie. is should be i.e. 
Signed-off-by: YuPengZTE <yu.peng36@zte.com.cn>
 2016-09-20 16:21:14 +08:00
Vish Kannan a1fe3adbc7 Revert "Revert "[kubelet] Fix oom-score-adj policy in kubelet"" 2016-09-16 16:32:58 -07:00
Vish Kannan 492ca3bc9c Revert "[kubelet] Fix oom-score-adj policy in kubelet" 2016-09-15 19:28:59 -07:00
Vishnu kannan e4acad7afb Fix oom-score-adj policy in kubelet. 
Docker daemon and kubelet needs to be protected by setting oom-score-adj to -999.

Signed-off-by: Vishnu kannan <vishnuk@google.com>
 2016-09-14 11:56:10 -07:00
Jordan Liggitt 620cc66ead
Doc API group suffix, add test to catch new groups 2016-09-09 15:56:08 -04:00
Matt Liggett 43d449b943 re-run update-munge-docs 2016-09-06 17:41:57 -07:00
Kubernetes Submit Queue d022750ad2 Merge pull request #31919 from ciwang/designdoc 
Automatic merge from submit-queue

Snapshotting design doc

<!--  Thanks for sending a pull request!  Here are some tips for you:
1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md
2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md
3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes
-->

**What this PR does / why we need it**:

Design doc for volume snapshotting feature (alpha)

**Special notes for your reviewer**:

**Release note**:
<!--  Steps to write your release note:
1. Use the release-note-* labels to set the release note state (if you have access) 
2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. 
-->
```release-note
```
 2016-09-03 09:11:19 -07:00
Kubernetes Submit Queue 8730514bd2 Merge pull request #31861 from YuPengZTE/devNote 
Automatic merge from submit-queue

The first letter is small

<!--  Thanks for sending a pull request!  Here are some tips for you:
1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md
2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md
3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes
-->

**What this PR does / why we need it**:

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #

**Special notes for your reviewer**:

**Release note**:
<!--  Steps to write your release note:
1. Use the release-note-* labels to set the release note state (if you have access) 
2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. 
-->
```release-note
```
 2016-09-03 09:11:15 -07:00
Cindy Wang 3a28c09efb Snapshotting design doc 
minor edits, changing prefix on annotations

update-munge-docs
 2016-09-02 13:39:50 -07:00
David McMahon 385fb81407 Update the latestReleaseBranch to release-1.4 in the munger. 2016-09-01 14:40:55 -07:00
YuPengZTE b367764167 The first letter is small 2016-09-01 17:23:21 +08:00
Kubernetes Submit Queue 1b184f29d0 Merge pull request #29287 from caitong93/patch-2 
Automatic merge from submit-queue

Fix a typo in resource-qos design doc
 2016-08-29 12:15:31 -07:00
Jeff Mendoza 95b73058d2 Removed non-md files from docs. Moved doc yamls to test/fixtures. 
Most of the contents of docs/ has moved to kubernetes.github.io.
Development of the docs and accompanying files has continued there, making
the copies in this repo stale. I've removed everything but the .md files
which remain to redirect old links. The .yaml config files in the docs
were used by some tests, these have been moved to test/fixtures/doc-yaml,
and can remain there to be used by tests or other purposes.
 2016-08-25 15:09:27 -07:00
yuexiao-wang 2d17b43361 Add targets for PHONY in Makefile 
Signed-off-by: yuexiao-wang <wang.yuexiao@zte.com.cn>
 2016-08-25 09:03:05 +08:00
Vladi 27458174bb Doc: Explain how to use EBS storage on AWS 2016-08-24 12:59:44 -07:00
Kubernetes Submit Queue 8ba1be314e Merge pull request #29785 from petemiron/patch-1 
Automatic merge from submit-queue

Clarify documentation that new admission control plugin must be imported

```release-note
```

Admission control design doc doesn't mention importing the plugin to plugins.go. I was unable to get the plugin to build into my binary without it. Updated documentation to prevent future confusion.
 2016-08-23 16:52:40 -07:00