Production-Grade Container Scheduling and Management
Go to file
Kubernetes Submit Queue 52df372f9b Merge pull request #35805 from dgoodwin/token-mgmt
Automatic merge from submit-queue

Implement kubeadm bootstrap token management

Creates bootstrap tokens as secrets per the specification in #30707 

_WARNING_: These are not currently hooked up to the discovery service or the token it creates.

Still TODO:
- [x] delete tokens
- [x] merge with #35144 and adopt it's testing approach
- [x] determine if we want wholesale json output & templating like kubectl (we do not have an API object with the data we want here) may require a bit of plumbing.
- [x] allow specifying a token duration on the CLI
- [x] allow configuring the default token duration
- [x] hook up the initial token created during init

Sample output:

```
(root@centos1 ~) $ kubeadm token create
Running pre-flight checks
<cmd/token> Token secret created: f6dc69.c43e491752c4a0fd
(root@centos1 ~) $ kubeadm token create
Running pre-flight checks
<cmd/token> Token secret created: 8fad2f.e7b78c8a5f7c7b9a
(root@centos1 ~) $ kubeadm token list  
Running pre-flight checks
ID        TOKEN                     EXPIRATION
44d805    44d805.a4e78b6cf6435e33   23h
4f65bb    4f65bb.d006a3c7a0e428c9   23h
6a086e    6a086e.2ff99f0823236b5b   23h
8fad2f    8fad2f.e7b78c8a5f7c7b9a   23h
f6dc69    f6dc69.c43e491752c4a0fd   23h
f81653    f81653.9ab82a2926c7e985   23h
```
2016-12-20 14:44:40 -08:00
.github
api Remove extensions/v1beta1 Job - generated changes 2016-12-17 00:07:25 +01:00
build Merge pull request #38984 from deads2k/fed-16-make-image 2016-12-20 07:05:40 -08:00
cluster Merge pull request #39010 from jszczepkowski/ha-validation-fix 2016-12-20 02:50:18 -08:00
cmd Merge pull request #35805 from dgoodwin/token-mgmt 2016-12-20 14:44:40 -08:00
docs Remove extensions/v1beta1 Job - generated changes 2016-12-17 00:07:25 +01:00
examples Update bazel 2016-12-16 17:49:23 +01:00
federation Merge pull request #39013 from xulike666/first-contributor-from-harmonycloud 2016-12-20 07:44:34 -08:00
Godeps Merge pull request #38625 from smarterclayton/bump_gorestful 2016-12-12 22:24:37 -08:00
hack Merge pull request #38984 from deads2k/fed-16-make-image 2016-12-20 07:05:40 -08:00
hooks remove hack/verify-munge-docs.sh from pre-commit hooks 2016-12-09 15:17:18 -08:00
logo
pkg Merge pull request #35805 from dgoodwin/token-mgmt 2016-12-20 14:44:40 -08:00
plugin add service status detection to kubernetes-discovery 2016-12-19 14:56:20 -05:00
staging Remove extensions/v1beta1 Job - staging client 2016-12-17 00:10:35 +01:00
test Merge pull request #38616 from shyamjvs/kubemark-gci-master 2016-12-20 00:36:21 -08:00
third_party add README file to the forked wal pkg 2016-12-16 16:33:44 -08:00
vendor Remove extensions/v1beta1 Job - staging client 2016-12-17 00:10:35 +01:00
.gazelcfg.json fix examples/ compilation so that test/ also compiles 2016-12-12 15:14:49 -08:00
.generated_docs kubectl: generated changes for new pdb command 2016-12-02 18:42:25 +01:00
.generated_files
.gitattributes
.gitignore
BUILD.bazel Rename build-tools/debs to build/debs 2016-12-15 11:10:23 -08:00
CHANGELOG.md Document known issue for broken local-up-cluster script in 1.5.1 2016-12-16 15:01:22 -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 Rename build-tools/ back to build/ 2016-12-14 13:42:15 -08:00
Makefile.generated_files
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 bazel: build debs for kubelet and kubeadm 2016-12-14 16:11:58 -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