Merge pull request #1 from kubernetes/master

Sync changes

.bazelversion

@@ -0,0 +1 @@
+build/root/.bazelversion

.generated_files

@@ -1,7 +1,7 @@
 # Files that should be ignored by tools which do not want to consider generated
 # code.
 #
-# https://github.com/kubernetes/contrib/blob/master/mungegithub/mungers/size.go
+# https://github.com/kubernetes/test-infra/blob/master/prow/plugins/size/size.go
 #
 # This file is a series of lines, each of the form:
 #     <type> <name>
@@ -24,7 +24,4 @@ file-name	types_swagger_doc_generated.go
 
 path-prefix	Godeps/
 path-prefix	vendor/
-path-prefix	api/swagger-spec/
 path-prefix	pkg/generated/
-
-paths-from-repo	docs/.generated_docs

.gitattributes

@@ -6,6 +6,5 @@ test/test_owners.csv merge=union
 **/generated.pb.go linguist-generated=true
 **/generated.proto
 **/types_swagger_doc_generated.go linguist-generated=true
-docs/api-reference/** linguist-generated=true
-api/swagger-spec/*.json linguist-generated=true
 api/openapi-spec/*.json linguist-generated=true
+staging/**/go.sum linguist-generated=true

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,29 @@
+---
+name: Bug Report
+about: Report a bug encountered while operating Kubernetes
+labels: kind/bug
+
+---
+
+<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
+
+If the matter is security related, please disclose it privately via https://kubernetes.io/security/
+-->
+
+
+**What happened**:
+
+**What you expected to happen**:
+
+**How to reproduce it (as minimally and precisely as possible)**:
+
+**Anything else we need to know?**:
+
+**Environment**:
+- Kubernetes version (use `kubectl version`):
+- Cloud provider or hardware configuration:
+- OS (e.g: `cat /etc/os-release`):
+- Kernel (e.g. `uname -a`):
+- Install tools:
+- Network plugin and version (if this is a network-related bug):
+- Others:

.github/ISSUE_TEMPLATE/enhancement.md

@@ -0,0 +1,11 @@
+---
+name: Enhancement Request
+about: Suggest an enhancement to the Kubernetes project
+labels: kind/feature
+
+---
+<!-- Please only use this template for submitting enhancement requests -->
+
+**What would you like to be added**:
+
+**Why is this needed**:

.github/ISSUE_TEMPLATE/failing-test.md

@@ -0,0 +1,20 @@
+---
+name: Failing Test
+about: Report continuously failing tests or jobs in Kubernetes CI
+labels: kind/failing-test
+
+---
+
+<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
+
+**Which jobs are failing**:
+
+**Which test(s) are failing**:
+
+**Since when has it been failing**:
+
+**Testgrid link**:
+
+**Reason for failure**:
+
+**Anything else we need to know**:

.github/ISSUE_TEMPLATE/flaking-test.md

@@ -0,0 +1,20 @@
+---
+name: Flaking Test
+about: Report flaky tests or jobs in Kubernetes CI
+labels: kind/flake
+
+---
+
+<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
+
+**Which jobs are flaking**:
+
+**Which test(s) are flaking**:
+
+**Testgrid link**:
+
+**Reason for failure**:
+
+**Anything else we need to know**:
+- links to go.k8s.io/triage appreciated
+- links to specific failures in spyglass appreciated

.github/ISSUE_TEMPLATE/support.md

@@ -0,0 +1,18 @@
+---
+name: Support Request
+about: Support request or question relating to Kubernetes
+labels: triage/support
+
+---
+
+<!--
+STOP -- PLEASE READ!
+
+GitHub is not the right place for support requests.
+
+If you're looking for help, check [Stack Overflow](https://stackoverflow.com/questions/tagged/kubernetes) and the [troubleshooting guide](https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/).
+
+You can also post your question on the [Kubernetes Slack](http://slack.k8s.io/) or the [Discuss Kubernetes](https://discuss.kubernetes.io/) forum.
+
+If the matter is security related, please disclose it privately via https://kubernetes.io/security/.
+-->

.github/OWNERS

@@ -1,12 +1,18 @@
+# See the OWNERS docs at https://go.k8s.io/owners
+
 reviewers:
   - castrojo
   - cblecker
-  - grodrigues3
+  - guineveresaenger
+  - mrbobbytables
+  - nikhita
   - parispittman
   - Phillels
 approvers:
   - castrojo
   - cblecker
-  - grodrigues3
+  - nikhita
   - parispittman
   - Phillels
+labels:
+  - sig/contributor-experience

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,19 +1,20 @@
 <!--  Thanks for sending a pull request!  Here are some tips for you:
-1. If this is your first time, read our contributor guidelines https://git.k8s.io/community/contributors/guide#your-first-contribution and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
+
+1. If this is your first time, please read our contributor guidelines: https://git.k8s.io/community/contributors/guide#your-first-contribution and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
 2. Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request. For reference on required PR/issue labels, read here:
-https://git.k8s.io/community/contributors/devel/release.md#issue-kind-label
-3. Ensure you have added or ran the appropriate tests for your PR: https://git.k8s.io/community/contributors/devel/testing.md
+https://git.k8s.io/community/contributors/devel/sig-release/release.md#issuepr-kind-label
+3. Ensure you have added or ran the appropriate tests for your PR: https://git.k8s.io/community/contributors/devel/sig-testing/testing.md
 4. If you want *faster* PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
-5. Follow the instructions for writing a release note: https://git.k8s.io/community/contributors/guide/release-notes.md
-6. If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests
+5. If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests
 -->
 
 **What type of PR is this?**
-> Uncomment only one, leave it on its own line:
+> Uncomment only one ` /kind <>` line, hit enter to put that in a new line, and remove leading whitespace from that line:
 >
 > /kind api-change
 > /kind bug
 > /kind cleanup
+> /kind deprecation
 > /kind design
 > /kind documentation
 > /kind failing-test
@@ -22,18 +23,45 @@ https://git.k8s.io/community/contributors/devel/release.md#issue-kind-label
 
 **What this PR does / why we need it**:
 
-**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
+**Which issue(s) this PR fixes**:
+<!--
+*Automatically closes linked issue when PR is merged.
+Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
+_If PR is about `failing-tests or flakes`, please post the related issues/tests in a comment and do not use `Fixes`_*
+-->
 Fixes #
 
 **Special notes for your reviewer**:
 
 **Does this PR introduce a user-facing change?**:
-<!--  
-If no, just write "NONE".
+<!--
+If no, just write "NONE" in the release-note block below.
 If yes, a release note is required:
 Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required".
-2. 
+
+For more information on release notes see: https://git.k8s.io/community/contributors/guide/release-notes.md
 -->
 ```release-note
 
 ```
+
+**Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.**:
+
+<!--
+This section can be blank if this pull request does not require a release note.
+
+When adding links which point to resources within git repositories, like
+KEPs or supporting documentation, please reference a specific commit and avoid
+linking directly to the master branch. This ensures that links reference a
+specific point in time, rather than a document that may change over time.
+
+See here for guidance on getting permanent links to files: https://help.github.com/en/articles/getting-permanent-links-to-files
+
+Please use the following format for linking documentation:
+- [KEP]: <link>
+- [Usage]: <link>
+- [Other doc]: <link>
+-->
+```docs
+
+```

.github/SECURITY.md

@@ -0,0 +1,14 @@
+# Security Policy
+
+## Supported Versions
+
+Information about supported Kubernetes versions can be found on the
+[Kubernetes version and version skew support policy] page on the Kubernetes website.
+
+## Reporting a Vulnerability
+
+Instructions for reporting a vulnerability can be found on the
+[Kubernetes Security and Disclosure Information] page.
+
+[Kubernetes version and version skew support policy]: https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-versions
+[Kubernetes Security and Disclosure Information]: https://kubernetes.io/docs/reference/issues-security/security/#report-a-vulnerability

.gitignore

@@ -113,6 +113,13 @@ kubernetes.tar.gz
 zz_generated.openapi.go
 zz_generated_*_test.go
 
+# TODO(roycaihw): remove this when we stop committing the generated definition
+!staging/src/k8s.io/apiextensions-apiserver/pkg/generated/openapi/zz_generated.openapi.go
+# low-change blueprint in code-generator to notice changes
+!staging/src/k8s.io/code-generator/_examples/apiserver/openapi/zz_generated.openapi.go
+# low-change sample-apiserver spec to be compilable when published
+!staging/src/k8s.io/sample-apiserver/pkg/generated/openapi/zz_generated.openapi.go
+
 # make-related metadata
 /.make/
 
@@ -127,3 +134,6 @@ zz_generated_*_test.go
 
 /bazel-*
 *.pyc
+
+# generated by verify-vendor.sh
+vendordiff.patch