aea995c45f
We are not sure why this was stdout, since stdin is what the user uses to pass information to the exec plugin. There is a question of backwards compatibility here. Our take is that this is a bug, and so we are ameliorating behavior instead of breaking behavior. There are 2 main cases to consider with respect to backwards compatibility: 1. an existing exec plugin depended on stdin being hooked up to them if stdout was a terminal (e.g., echo foo | client-go-command-line-tool); we believe this is an anti-pattern, since the client-go-command-line-tool could be using stdin elsewhere (e.g., echo foo | kubectl apply -f -) 2. an existing exec plugin depended on stdin not being hooked up to them if stdout was not a terminal (e.g., client-go-command-line-tool >/dev/null); hopefully there are very few plugins that have tried to base logic off of whether stdin returned EOF immediately, since this could also happen when something else is wrong with stdin We hope to apply a stronger fix to this exec plugin user interaction stuff in a future release. Signed-off-by: Andrew Keesler <akeesler@vmware.com> |
||
|---|---|---|
| .github | ||
| api | ||
| build | ||
| CHANGELOG | ||
| cluster | ||
| cmd | ||
| docs | ||
| hack | ||
| LICENSES | ||
| logo | ||
| pkg | ||
| plugin | ||
| staging | ||
| test | ||
| third_party | ||
| translations | ||
| vendor | ||
| .generated_files | ||
| .gitattributes | ||
| .gitignore | ||
| CHANGELOG.md | ||
| code-of-conduct.md | ||
| CONTRIBUTING.md | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| Makefile | ||
| Makefile.generated_files | ||
| OWNERS | ||
| OWNERS_ALIASES | ||
| README.md | ||
| SECURITY_CONTACTS | ||
| SUPPORT.md | ||
Kubernetes (K8s)
Kubernetes, also known as K8s, is an open source system for managing containerized applications across multiple hosts. It provides basic mechanisms for deployment, maintenance, and scaling of applications.
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.
Kubernetes is hosted by the Cloud Native Computing Foundation (CNCF). If your company wants to help shape the evolution of technologies that are container-packaged, dynamically scheduled, and microservices-oriented, consider joining the CNCF. For details about who's involved and how Kubernetes plays a role, read the CNCF announcement.
To start using K8s
See our documentation on kubernetes.io.
Try our interactive tutorial.
Take a free course on Scalable Microservices with Kubernetes.
To use Kubernetes code as a library in other applications, see the list of published components.
Use of the k8s.io/kubernetes module or k8s.io/kubernetes/... packages as libraries is not supported.
To start developing K8s
The community repository hosts all information about building Kubernetes from source, how to contribute code and documentation, who to contact about what, etc.
If you want to build Kubernetes right away there are two options:
You have a working Go environment.
mkdir -p $GOPATH/src/k8s.io
cd $GOPATH/src/k8s.io
git clone https://github.com/kubernetes/kubernetes
cd kubernetes
make
You have a working Docker environment.
git clone https://github.com/kubernetes/kubernetes
cd kubernetes
make quick-release
For the full story, head over to the developer's documentation.
Support
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.