Production-Grade Container Scheduling and Management
Go to file
Ben Luddy fc02d1eaf5 Use per-policy marker names for VAP integration tests.
Writes to policy resources don't instantaneously take effect in admission. ValidatingAdmissionPolicy
integration tests determine that the policies under test have taken effect by adding a sentinel
policy rule and polling until that rule is applied to a request.

If the marker resource names are the same for each test case in a series of test cases, then
observing a policy's effect on a marker request only indicates that _any_ test policy is in effect,
but it's not necessarily the policy the current test case is waiting for. For example:

1. Test 1 creates a policy and binding.

2. The policy and binding are observed by the admission plugin and take effect.

3. Test 1 observes that a policy is in effect via marker requests.

4. Test 1 exercises the behavior under test and successfully deletes the policy and binding it
created.

5. Test 2 creates a policy and binding.

6. Test 2 observes that a policy is in effect via marker requests, but the policy in effect is still
the one created by Test 1.

7. Test 2 exercises the behavior under test, which fails because it was evaluated against Test 1's
policy.

Generating a per-policy name for the marker resource in each test resolves the timing issue. In the
example, step (6) will not proceed until the admission plugin has observed the policy and binding
created in (5).
2025-07-10 10:13:27 +02:00
.github Add new contribex leads to sig-contribex-approvers 2023-04-10 12:34:03 +05:30
api fix v1a3 ResourceSliceList metadata field name 2024-08-17 12:12:57 -07:00
build Bump images, dependencies and versions to go 1.23.10 and distroless iptables 2025-06-11 08:30:46 +02:00
CHANGELOG Update CHANGELOG/CHANGELOG-1.31.md for v1.31.10 2025-06-17 18:55:04 +00:00
cluster Update cni-plugins to v1.5.1 2024-08-29 09:13:54 +02:00
cmd Add check to see if promote worked within the retry loop 2025-06-13 10:05:33 +03:00
docs Make root approval non-recursive 2022-10-10 08:26:53 -04:00
hack Honor KUBE_HACK_TOOLS_GOTOOLCHAIN 2025-02-14 12:57:36 -05:00
LICENSES Switch to stretchr/testify / mockery for mocks 2024-06-20 19:42:53 +02:00
logo logo: better alignment of layers 2022-10-19 12:17:25 -07:00
pkg Clean backoff record earlier 2025-06-06 20:58:34 +00:00
plugin add missing RBAC to statefulset-controller for StatefulSetAutoDeletePVC feature 2024-09-02 14:40:40 +02:00
staging Bump images, dependencies and versions to go 1.23.10 and distroless iptables 2025-06-11 08:30:46 +02:00
test Use per-policy marker names for VAP integration tests. 2025-07-10 10:13:27 +02:00
third_party agnhost: merge registry.k8s.io/stress:v1 (github.com/vishh/stress) 2024-02-13 23:21:05 +09:00
vendor update coredns/corefile-migration to v1.0.23 to support coredns v1.11.3 2024-08-19 14:31:56 -07:00
.generated_files remove clearly unnecessary lingering BUILD file references 2022-10-04 16:47:25 -07:00
.gitattributes gitattributes: json and yaml files LF line endings 2022-12-22 11:36:07 +00:00
.gitignore Generate go.work files 2024-02-29 00:22:06 -08:00
.go-version Bump images, dependencies and versions to go 1.23.10 and distroless iptables 2025-06-11 08:30:46 +02:00
CHANGELOG.md
code-of-conduct.md
CONTRIBUTING.md
go.mod update vendor 2024-08-29 00:08:09 +00:00
go.sum update coredns/corefile-migration to v1.0.23 to support coredns v1.11.3 2024-08-19 14:31:56 -07:00
go.work Revert "Revert "remove legacycloudproviders from staging"" 2024-05-15 20:10:09 +08:00
go.work.sum update coredns/corefile-migration to v1.0.23 to support coredns v1.11.3 2024-08-19 14:31:56 -07:00
LICENSE
Makefile
OWNERS Add sig-architecture-approvers and dep-approvers to root dir 2022-10-10 13:43:04 -04:00
OWNERS_ALIASES Merge pull request #125122 from chendave/emeritus_2 2024-06-24 08:43:12 -07:00
README.md Get rid of most references to GOPATH 2024-02-29 22:06:51 -08:00
SECURITY_CONTACTS Update SECURITY_CONTACTS 2023-10-10 14:45:43 +00:00
SUPPORT.md Update SUPPORT.md 2022-06-27 16:58:44 +02:00

Kubernetes (K8s)

CII Best Practices Go Report Card GitHub release (latest SemVer)


Kubernetes, also known as K8s, is an open source system for managing containerized applications across multiple hosts. It provides basic mechanisms for the 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.

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.
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.

Community Meetings

The Calendar has the list of all the meetings in the Kubernetes community in a single location.

Adopters

The User Case Studies website has real-world use cases of organizations across industries that are deploying/migrating to Kubernetes.

Governance

Kubernetes project is governed by a framework of principles, values, policies and processes to help our community and constituents towards our shared goals.

The Kubernetes Community is the launching point for learning about how we organize ourselves.

The Kubernetes Steering community repo is used by the Kubernetes Steering Committee, which oversees governance of the Kubernetes project.

Roadmap

The Kubernetes Enhancements repo provides information about Kubernetes releases, as well as feature tracking and backlogs.