8cb84feef3
A previous PR replaced the usage of Redis in the guestbook app test with Agnhost. The replacement went well for Linux setups and Containers, which is why the tests are green, but there is a network particularity on Windows setups which won't allow the test to pass. The issue was observed with another test hitting the same issue: https://github.com/kubernetes/kubernetes/issues/83072 Here's exactly what happens during the test: - frontend containers are created, having the /guestbook endpoint. Its main purpose is to forward the call to either agnhost-master (cmd=set), or agnhost-slave (cmd=get). - agnhost-master container is created, having the /set endpoint, and the /register endpoint, through which the agnhost-slave containers would register to it. Its purpose is to propagate all data received through /set to its clients. - agnhost-slave containers are created, having the /set and /get endpoints. They would register to agnhost-master, and then receive any and all updates from it, which was then served through the /get endpoint. For simplicity, all 3 types have the same agnhost subcommand (agnhost guestbook), being able to satisfy its given purpose. For this, HTTP servers were being used, including for the /register endpoints. agnhost-master would send its /set updates as /set HTTP requests. However, because of the issue listed above, agnhost-master did not receive the client's IP, but rather the container host's IP, resulting in the request being sent to the wrong destination. This PR updates the agnhost guestbook subcommand. Now, the agnhost subscriber nodes will send their own IP to the /register endpoint (/endpoint?host=myip). |
||
|---|---|---|
| .github | ||
| api | ||
| build | ||
| CHANGELOG | ||
| cluster | ||
| cmd | ||
| docs | ||
| Godeps | ||
| hack | ||
| logo | ||
| pkg | ||
| plugin | ||
| staging | ||
| test | ||
| third_party | ||
| translations | ||
| vendor | ||
| .bazelrc | ||
| .bazelversion | ||
| .generated_files | ||
| .gitattributes | ||
| .gitignore | ||
| .kazelcfg.json | ||
| BUILD.bazel | ||
| 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 | ||
| WORKSPACE | ||
Kubernetes
Kubernetes 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 Kubernetes
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 Kubernetes
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.