Production-Grade Container Scheduling and Management
Go to file
Kubernetes Submit Queue d478eafa0c Merge pull request #39512 from ixdy/bazel-srcs-infinite-loop
Automatic merge from submit-queue

Generate a dummy BUILD file in _output/local/go to keep Bazel out of trouble

**What this PR does / why we need it**: the Kubernetes build system creates a symlink from `_output/local/go/src/k8s.io/kubernetes` back to `$KUBE_ROOT`, likely to deal with folks that don't have their `GOPATH `set up correctly.

Bazel's `glob()` is not very smart, and runs into issues with this; the `package-srcs` glob in `//BUILD.bazel` first evaluates the `**` before matching any excludes, and thus explodes on the infinite loop.

By generating a `BUILD` file along the path to the symlink, Bazel treats this as a separate package and descends no further.

(Oddly, generating a `BUILD.bazel` file doesn't seem to solve the glob explosion, but a directory with a `BUILD.bazel` file is still treated as a separate package. There's probably a subtle bug in Bazel somewhere.)

**Release note**:

```release-note
NONE
```
2017-01-06 14:57:35 -08:00
.github
api Merge pull request #39466 from kubernetes/bugfix 2017-01-06 11:30:11 -08:00
build Merge pull request #39492 from mikedanese/xtables 2017-01-06 00:23:38 -08:00
cluster Merge pull request #39520 from shyamjvs/add-etcd-events-log 2017-01-06 12:22:09 -08:00
cmd Merge pull request #39490 from deads2k/generic-16-bump-gengo 2017-01-06 11:30:13 -08:00
docs Enable auto-generating sources rules 2017-01-05 14:14:13 -08:00
examples Move provisioning examples out of 'experimental' directory. 2017-01-06 13:58:04 +01:00
federation Merge pull request #39490 from deads2k/generic-16-bump-gengo 2017-01-06 11:30:13 -08:00
Godeps bump(k8s.io/gengo): 8dd9c9e5e82c3cca687497c3cd7ac90e702c7c21 2017-01-05 16:20:00 -05:00
hack Generate a dummy BUILD file in _output/local/go to keep Bazel out of trouble 2017-01-05 22:05:17 -08:00
hooks Fix spelling in package naming linter error message 2016-12-20 15:48:14 -05:00
logo
pkg Merge pull request #39318 from NickrenREN/eviction-manager-start 2017-01-06 11:55:41 -08:00
plugin Enable auto-generating sources rules 2017-01-05 14:14:13 -08:00
staging mechanicals 2017-01-05 11:14:27 -05:00
test Merge pull request #39349 from shyamjvs/rbac-for-kubemark 2017-01-06 13:42:54 -08:00
third_party Enable auto-generating sources rules 2017-01-05 14:14:13 -08:00
translations Add initial translation support. 2016-12-23 20:45:52 -08:00
vendor Merge pull request #39490 from deads2k/generic-16-bump-gengo 2017-01-06 11:30:13 -08:00
.gazelcfg.json Generate a dummy BUILD file in _output/local/go to keep Bazel out of trouble 2017-01-05 22:05:17 -08:00
.generated_docs add create rolebinding 2016-12-21 09:03:27 -05:00
.generated_files
.gitattributes
.gitignore
BUILD.bazel Add a rule to create kubernetes-src.tar.gz 2017-01-05 14:14:13 -08:00
CHANGELOG.md Update CHANGELOG.md 2016-12-28 12:35:39 -08:00
code-of-conduct.md
CONTRIBUTING.md updated munge-docs 2016-11-29 01:35:11 -08:00
labels.yaml
LICENSE LICENSE: revert modifications to Apache license 2016-11-22 11:44:46 -08:00
Makefile Adding test-federation-cmd.sh to test kubectl with federation apiserver 2017-01-04 11:17:05 -08:00
Makefile.generated_files Remove a from each codegen path 2016-12-30 18:44:32 -08:00
OWNERS
OWNERS_ALIASES Update OWNERS: Create test-infra-maintainers 2016-12-19 15:41:51 -08:00
README.md Update README.md 2016-12-20 08:51:06 -06:00
Vagrantfile
WORKSPACE add netlink and libxtables to kube-proxy image 2017-01-05 13:42:26 -08:00

Kubernetes

Submit Queue Widget GoDoc Widget Coverage Status Widget

Introduction

Kubernetes is an open source system for managing containerized applications across multiple hosts, providing basic mechanisms for deployment, maintenance, and scaling of applications. Kubernetes is hosted by the Cloud Native Computing Foundation (CNCF)

Kubernetes builds upon a decade and a half of experience at Google running production workloads at scale using a system called Borg, combined with best-of-breed ideas and practices from the community.


Are you ...

Code of Conduct

The Kubernetes community abides by the CNCF code of conduct. Here is an excerpt:

As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.

Community

Do you want to help "shape the evolution of technologies that are container-packaged, dynamically-scheduled and microservices-oriented? ". If you are a company, you should consider joining the CNCF. For details about who's involved in CNCF and how Kubernetes plays a role, read the announcement. For general information about our community see the website community page.

Join us on social media (Twitter, Google+) and read our blog

Ask questions and help answer them on Slack or Stack Overflow

Attend our key events (kubecon, cloudnativecon, weekly community meeting)

Join a Special Interest Group (SIG)

Contribute

If you're interested in being a contributor and want to get involved in developing Kubernetes, get started with this reading:

You will then most certainly gain a lot from joining a SIG, attending the regular hangouts as well as the community meeting.

If you have an idea for a new feature, see the Kubernetes Features repository for a list of features that are coming in new releases as well as details on how to propose one.

Building Kubernetes for the impatient

If you want to build Kubernetes right away there are two options:

$ go get -d k8s.io/kubernetes
$ cd $GOPATH/src/k8s.io/kubernetes
$ make
$ git clone https://github.com/kubernetes/kubernetes
$ cd kubernetes
$ make quick-release

If you are less impatient, head over to the developer's documentation.

Support

While there are many different channels that you can use to get hold of us (Slack, Stack Overflow, Issues, Forums/Mailing lists), you can help make sure that we are efficient in getting you the help that you need.

If you need support, start with the troubleshooting guide and work your way through the process that we've outlined.

That said, if you have questions, reach out to us one way or another. We don't bite!

Analytics