eb43cd5eb3
Automatic merge from submit-queue (batch tested with PRs 43313, 43257, 43271, 43307) Remove 'all namespaces' meaning of empty list in PodAffinityTerm Removes the distinction between `null` and `[]` for the PodAffinityTerm#namespaces field (option 4 discussed in https://github.com/kubernetes/kubernetes/issues/43203#issuecomment-287237992), since we can't distinguish between them in protobuf (and it's a less than ideal API) Leaves the door open to reintroducing "all namespaces" function via a dedicated field or a dedicated token in the list of namespaces Wanted to get a PR open and tests green in case we went with this option. Not sure what doc/release-note is needed if the "all namespaces" function is not present in 1.6
Kubernetes Documentation: releases.k8s.io/HEAD
-
The User's guide is for anyone who wants to run programs and services on an existing Kubernetes cluster.
-
The Cluster Admin's guide is for anyone setting up a Kubernetes cluster or administering it.
-
The Developer guide is for anyone wanting to write programs that access the Kubernetes API, write plugins or extensions, or modify the core code of Kubernetes.
-
The Kubectl Command Line Interface is a detailed reference on the
kubectlCLI. -
The API object documentation is a detailed description of all fields found in core API objects.
-
An overview of the Design of Kubernetes
-
There are example files and walkthroughs in the examples folder.
-
If something went wrong, see the troubleshooting guide for how to debug. You should also check the known issues for the release you're using.
-
To report a security issue, see Reporting a Security Issue.