bc861bf756
Automatic merge from submit-queue (batch tested with PRs 39475, 38666, 39327, 38396, 39613) Create k8s.io/apimachinery repo Don't panic. The diff is quite large, but its all generated change. The first few commits are where are all the action is. I built a script to find the fanout from ``` k8s.io/kubernetes/pkg/apimachinery/registered k8s.io/kubernetes/pkg/runtime/serializer k8s.io/kubernetes/pkg/runtime/serializer/yaml k8s.io/kubernetes/pkg/runtime/serializer/streaming k8s.io/kubernetes/pkg/runtime/serializer/recognizer/testing ``` It copied ``` k8s.io/kubernetes/pkg/api/meta k8s.io/kubernetes/pkg/apimachinery k8s.io/kubernetes/pkg/apimachinery/registered k8s.io/kubernetes/pkg/apis/meta/v1 k8s.io/kubernetes/pkg/apis/meta/v1/unstructured k8s.io/kubernetes/pkg/conversion k8s.io/kubernetes/pkg/conversion/queryparams k8s.io/kubernetes/pkg/genericapiserver/openapi/common - this needs to renamed post-merge. It's just types k8s.io/kubernetes/pkg/labels k8s.io/kubernetes/pkg/runtime k8s.io/kubernetes/pkg/runtime/schema k8s.io/kubernetes/pkg/runtime/serializer k8s.io/kubernetes/pkg/runtime/serializer/json k8s.io/kubernetes/pkg/runtime/serializer/protobuf k8s.io/kubernetes/pkg/runtime/serializer/recognizer k8s.io/kubernetes/pkg/runtime/serializer/recognizer/testing k8s.io/kubernetes/pkg/runtime/serializer/streaming k8s.io/kubernetes/pkg/runtime/serializer/versioning k8s.io/kubernetes/pkg/runtime/serializer/yaml k8s.io/kubernetes/pkg/selection k8s.io/kubernetes/pkg/types k8s.io/kubernetes/pkg/util/diff k8s.io/kubernetes/pkg/util/errors k8s.io/kubernetes/pkg/util/framer k8s.io/kubernetes/pkg/util/json k8s.io/kubernetes/pkg/util/net k8s.io/kubernetes/pkg/util/runtime k8s.io/kubernetes/pkg/util/sets k8s.io/kubernetes/pkg/util/validation k8s.io/kubernetes/pkg/util/validation/field k8s.io/kubernetes/pkg/util/wait k8s.io/kubernetes/pkg/util/yaml k8s.io/kubernetes/pkg/watch k8s.io/kubernetes/third_party/forked/golang/reflect ``` The script does the import rewriting and gofmt. Then you do a build, codegen, bazel update, and it produces all the updates. If we agree this is the correct approach. I'll create a verify script to make sure that no one messes with any files in the "dead" packages above. @kubernetes/sig-api-machinery-misc @smarterclayton @sttts @lavalamp @caesarxuchao `staging/prime-apimachinery.sh && hack/update-codegen.sh && nice make WHAT="federation/cmd/federation-apiserver/ cmd/kube-apiserver" && hack/update-openapi-spec.sh && hack/update-federation-openapi-spec.sh && hack/update-codecgen.sh && hack/update-codegen.sh && hack/update-generated-protobuf.sh && hack/update-bazel.sh` |
||
|---|---|---|
| .github | ||
| api | ||
| build | ||
| cluster | ||
| cmd | ||
| docs | ||
| examples | ||
| federation | ||
| Godeps | ||
| hack | ||
| hooks | ||
| logo | ||
| pkg | ||
| plugin | ||
| staging | ||
| test | ||
| third_party | ||
| translations | ||
| vendor | ||
| .gazelcfg.json | ||
| .generated_docs | ||
| .generated_files | ||
| .gitattributes | ||
| .gitignore | ||
| BUILD.bazel | ||
| CHANGELOG.md | ||
| code-of-conduct.md | ||
| CONTRIBUTING.md | ||
| labels.yaml | ||
| LICENSE | ||
| Makefile | ||
| Makefile.generated_files | ||
| OWNERS | ||
| OWNERS_ALIASES | ||
| README.md | ||
| Vagrantfile | ||
| WORKSPACE | ||
Kubernetes
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 ...
- Interested in learning more about using Kubernetes?
- See our documentation on kubernetes.io
- Try our interactive tutorial
- Take a free course on Scalable Microservices with Kubernetes.
- Interested in developing the core Kubernetes code base, developing tools using the Kubernetes API or helping in anyway possible ? Keep reading!
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:
- The community expectations
- The contributor guidelines
- The Kubernetes Developer Guide
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:
- You have a working Go environment.
$ go get -d k8s.io/kubernetes
$ cd $GOPATH/src/k8s.io/kubernetes
$ make
- You have a working Docker environment.
$ 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!