6ae9266759
Automatic merge from submit-queue (batch tested with PRs 38173, 38151, 38197, 38221) Include resource type headers in diff report **What this PR does / why we need it**: when checking for leaked resources, we report a failure only if there were additions to the diff - we don't want resources that were deleted during the run to count as a failure. The logic for this removes the resource type headers from the diff report, however, so it's harder to understand what leaked. For example, in https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gke-alpha-features-release-1.5/196/, the test failure shows ``` Error: 4 leaked resources +NAME REGION IP_ADDRESS IP_PROTOCOL TARGET +a66878dbaad1f11e695b342010af0002 us-central1 104.198.182.83 TCP us-central1/targetPools/a66878dbaad1f11e695b342010af0002 +NAME REGION SESSION_AFFINITY BACKUP HEALTH_CHECKS +a66878dbaad1f11e695b342010af0002 us-central1 a66878dbaad1f11e695b342010af0002 ``` but the [actual diff](https://storage.googleapis.com/kubernetes-jenkins/logs/ci-kubernetes-e2e-gke-alpha-features-release-1.5/196/artifacts/gcp-resources-diff.txt) contains more information: ``` --- /workspace/_artifacts/gcp-resources-before.txt 2016-12-01 14:39:14.260049037 -0800 +++ /workspace/_artifacts/gcp-resources-after.txt 2016-12-01 14:39:14.260049037 -0800 @@ -34,8 +34 @@ [ addresses ] -NAME REGION ADDRESS STATUS -a03d0e020a6bc11e6855f42010af0001 us-central1 104.197.135.88 RESERVED -a23f20a47a6a011e6829a42010af0004 us-central1 104.197.147.212 RESERVED -a32291b51a5e611e6b73342010af0002 us-central1 104.198.171.178 RESERVED -a3c93cf79a65811e6b7c242010af0001 us-central1 104.198.58.57 RESERVED -a9ac5bd1ba62811e68d1142010af0004 us-central1 104.154.134.135 RESERVED -adae4c1a7a69511e6b2df42010af0000 us-central1 104.198.182.83 RESERVED -adb4a80caa60311e689a942010af0001 us-central1 104.154.116.195 RESERVED + @@ -64 +57,2 @@ [ forwarding-rules ] - +NAME REGION IP_ADDRESS IP_PROTOCOL TARGET +a66878dbaad1f11e695b342010af0002 us-central1 104.198.182.83 TCP us-central1/targetPools/a66878dbaad1f11e695b342010af0002 @@ -68 +62,2 @@ [ target-pools ] - +NAME REGION SESSION_AFFINITY BACKUP HEALTH_CHECKS +a66878dbaad1f11e695b342010af0002 us-central1 a66878dbaad1f11e695b342010af0002 ``` This PR will include the `[ type header ]`s in the report if resources are leaked. cc @fejta |
||
|---|---|---|
| .github | ||
| api | ||
| build-tools | ||
| cluster | ||
| cmd | ||
| docs | ||
| examples | ||
| federation | ||
| Godeps | ||
| hack | ||
| hooks | ||
| logo | ||
| pkg | ||
| plugin | ||
| staging | ||
| test | ||
| third_party | ||
| vendor | ||
| .gazelcfg.json | ||
| .generated_docs | ||
| .generated_files | ||
| .gitattributes | ||
| .gitignore | ||
| BUILD | ||
| 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 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 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.
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!