Production-Grade Container Scheduling and Management
Go to file
Kubernetes Submit Queue 70296869e9 Merge pull request #36919 from Random-Liu/remove-dependency-on-flags
Automatic merge from submit-queue

Node E2E: Remove kubelet related flags

This PR:
1. **Add `KubeletConfig` in test context.** The configuration is dynamically retrieved from kubelet `configz/` endpoint after test node registers itself.
2. **Change tests to look at `KubeletConfig` instead of other kubelet related fields in test context.**
3. **Remove kubelet related flags from node e2e.** Add `kubelet-flags` to pass kubelet flags all together.

Why do we need this change?
1. This is required by **node soaking test and node conformance test**.
  * **For node soaking test.** We'll have one job start the test environment, and another job running the actual test again and again. It's hard to tell the test by flag how kubelet is configured.
  * **For node conformance test.** Kubelet is usually started by user. It's hard and troublesome to tell the test by flag how kubelet is configured.
2. **No need to add another flag in node e2e for each kubelet flag we want to set in the test.** Just directly add the kubelet flag into `kubelet-flags`.

In the future,
1. Kubelet start logic should be moved outside of the test. We should have standard kubelet launcher or standard cloud-init node setup script etc.
2. The test should validate kubelet configuration:
  * Whether the configuration is production ready?
  * Whether the configuration has conflicts?
  * Whether some configuration conflict with node e2e/conformance test is turned on (cloud provider etc.)? (Some configurations need to be turned off when running node e2e/conformance test)
  * ...

/cc @kubernetes/sig-node
2016-11-17 11:32:57 -08:00
.github Fix PR template 2016-11-11 14:48:58 -08:00
api Auto-generated OpenAPI spec 2016-11-11 16:30:07 -08:00
build-tools bump golang to 1.7.3 2016-11-09 11:48:28 -08:00
cluster Merge pull request #36993 from Crassirostris/docker-logs-time-format 2016-11-17 10:26:59 -08:00
cmd Merge pull request #36767 from vishh/rename-cgroups-flags 2016-11-14 17:35:19 -08:00
contrib
docs Delete gotest-dockerized 2016-11-15 13:11:04 -08:00
examples Remove namespaces from all examples. 2016-11-11 11:57:33 -08:00
federation Merge pull request #36336 from justinsb/federation_dns_hosted_zone_2 2016-11-17 00:49:09 -08:00
Godeps Photon Controller platform vendor code 2016-11-08 09:36:16 -08:00
hack Remove kubelet related flags from node e2e. Add a single flag kubelet-flags to pass kubelet flags all together. 2016-11-17 10:17:32 -08:00
hooks Add verify script federation OpenAPI spec generation 2016-11-07 02:41:50 -08:00
logo
pkg Merge pull request #36965 from Random-Liu/fix-truncate-hostname 2016-11-17 02:03:31 -08:00
plugin Merge pull request #36210 from justinsb/flex_node_conditions 2016-11-15 01:02:01 -08:00
staging Updated stating client go 2016-11-11 19:40:31 +01:00
test Update bazel. 2016-11-17 10:18:00 -08:00
third_party
vendor Updated bazel build 2016-11-11 19:43:06 +01:00
www
.generated_docs autogenerated 2016-11-08 06:33:46 -08:00
.generated_files List generated files for the github size munger 2016-11-15 15:47:22 -08:00
.gitattributes Move .gitattributes annotation to the root, so GitHub will respect them. 2016-11-02 09:48:45 -07:00
.gitignore
BUILD
CHANGELOG.md Update CHANGELOG.md for v1.4.6. 2016-11-11 21:52:53 -08:00
code-of-conduct.md
CONTRIB.md
CONTRIBUTING.md
DESIGN.md
labels.yaml
LICENSE
Makefile [kubelet]update --cgroups-per-qos to --experimental-cgroups-per-qos 2016-11-15 15:55:47 +08:00
Makefile.generated_files Verify generated files 2016-11-01 22:10:25 -07:00
OWNERS
OWNERS_ALIASES
README.md Merge pull request #36595 from philips/fix-all-the-readme-links 2016-11-11 15:14:09 -08:00
Vagrantfile
WORKSPACE

Kubernetes

Submit Queue Widget GoDoc Widget Coverage Status Widget

Are you ...


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:

  • lean: lightweight, simple, accessible
  • portable: public, private, hybrid, multi cloud
  • extensible: modular, pluggable, hookable, composable
  • self-healing: auto-placement, auto-restart, auto-replication

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


Kubernetes is ready for Production!

Since the Kubernetes 1.0 release in July 2015 Kubernetes is ready for your production workloads.

Kubernetes can run anywhere!

You can run Kubernetes on your local workstation under Vagrant, cloud providers (e.g. GCE, AWS, Azure), and physical hardware. Essentially, anywhere Linux runs you can run Kubernetes. Checkout the Getting Started Guides for details.

Concepts

Kubernetes works with the following concepts:

Cluster
A cluster is a set of physical or virtual machines and other infrastructure resources used by Kubernetes to run your applications. Kubernetes can run anywhere! See the Getting Started Guides for instructions for a variety of services.
Node
A node is a physical or virtual machine running Kubernetes, onto which pods can be scheduled.
Pod
Pods are a colocated group of application containers with shared volumes. They're the smallest deployable units that can be created, scheduled, and managed with Kubernetes. Pods can be created individually, but it's recommended that you use a replication controller even if creating a single pod.
Replication controller
Replication controllers manage the lifecycle of pods. They ensure that a specified number of pods are running at any given time, by creating or killing pods as required.
Service
Services provide a single, stable name and address for a set of pods. They act as basic load balancers.
Label
Labels are used to organize and select groups of objects based on key:value pairs.

Documentation

Kubernetes documentation is organized into several categories.

Community, discussion, contribution, and support

See which companies are committed to driving quality in Kubernetes on our community page.

Do you want to help "shape the evolution of technologies that are container packaged, dynamically scheduled and microservices oriented?"

You should consider joining the Cloud Native Computing Foundation. For details about who's involved and how Kubernetes plays a role, read their announcement.

Code of conduct

Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.

Are you ready to add to the discussion?

We have presence on:

You can also view recordings of past events and presentations on our Media page.

For Q&A, our threads are at:

Want to contribute to Kubernetes?

If you're interested in being a contributor and want to get involved in developing Kubernetes, start in the Kubernetes Developer Guide and also review the contributor guidelines.

Or, if you just have an idea for a new feature, see the Kubernetes Features repository for details on how to propose it.

Also, please see our expectations for members of the Kubernetes community.

Support

While there are many different channels that you can use to get ahold of us, 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!

Community resources

You can find more projects, tools and articles related to Kubernetes on the awesome-kubernetes list. Add your project there and help us make it better.

Instructive & educational resources for the Kubernetes community. By the community.

  • Community Documentation

Here you can learn more about the current happenings in the kubernetes community.

Analytics