bc861bf756
Automatic merge from submit-queue (batch tested with PRs 39475, 38666, 39327, 38396, 39613) Create k8s.io/apimachinery repo Don't panic. The diff is quite large, but its all generated change. The first few commits are where are all the action is. I built a script to find the fanout from ``` k8s.io/kubernetes/pkg/apimachinery/registered k8s.io/kubernetes/pkg/runtime/serializer k8s.io/kubernetes/pkg/runtime/serializer/yaml k8s.io/kubernetes/pkg/runtime/serializer/streaming k8s.io/kubernetes/pkg/runtime/serializer/recognizer/testing ``` It copied ``` k8s.io/kubernetes/pkg/api/meta k8s.io/kubernetes/pkg/apimachinery k8s.io/kubernetes/pkg/apimachinery/registered k8s.io/kubernetes/pkg/apis/meta/v1 k8s.io/kubernetes/pkg/apis/meta/v1/unstructured k8s.io/kubernetes/pkg/conversion k8s.io/kubernetes/pkg/conversion/queryparams k8s.io/kubernetes/pkg/genericapiserver/openapi/common - this needs to renamed post-merge. It's just types k8s.io/kubernetes/pkg/labels k8s.io/kubernetes/pkg/runtime k8s.io/kubernetes/pkg/runtime/schema k8s.io/kubernetes/pkg/runtime/serializer k8s.io/kubernetes/pkg/runtime/serializer/json k8s.io/kubernetes/pkg/runtime/serializer/protobuf k8s.io/kubernetes/pkg/runtime/serializer/recognizer k8s.io/kubernetes/pkg/runtime/serializer/recognizer/testing k8s.io/kubernetes/pkg/runtime/serializer/streaming k8s.io/kubernetes/pkg/runtime/serializer/versioning k8s.io/kubernetes/pkg/runtime/serializer/yaml k8s.io/kubernetes/pkg/selection k8s.io/kubernetes/pkg/types k8s.io/kubernetes/pkg/util/diff k8s.io/kubernetes/pkg/util/errors k8s.io/kubernetes/pkg/util/framer k8s.io/kubernetes/pkg/util/json k8s.io/kubernetes/pkg/util/net k8s.io/kubernetes/pkg/util/runtime k8s.io/kubernetes/pkg/util/sets k8s.io/kubernetes/pkg/util/validation k8s.io/kubernetes/pkg/util/validation/field k8s.io/kubernetes/pkg/util/wait k8s.io/kubernetes/pkg/util/yaml k8s.io/kubernetes/pkg/watch k8s.io/kubernetes/third_party/forked/golang/reflect ``` The script does the import rewriting and gofmt. Then you do a build, codegen, bazel update, and it produces all the updates. If we agree this is the correct approach. I'll create a verify script to make sure that no one messes with any files in the "dead" packages above. @kubernetes/sig-api-machinery-misc @smarterclayton @sttts @lavalamp @caesarxuchao `staging/prime-apimachinery.sh && hack/update-codegen.sh && nice make WHAT="federation/cmd/federation-apiserver/ cmd/kube-apiserver" && hack/update-openapi-spec.sh && hack/update-federation-openapi-spec.sh && hack/update-codecgen.sh && hack/update-codegen.sh && hack/update-generated-protobuf.sh && hack/update-bazel.sh`
Cluster Federation
Kubernetes Cluster Federation enables users to federate multiple Kubernetes clusters. Please see the user guide and the admin guide for more details about setting up and using the Cluster Federation.
Building Kubernetes Cluster Federation
Please see the Kubernetes Development Guide
for initial setup. Once you have the development environment setup
as explained in that guide, you also need to install jq
Building cluster federation artifacts should be as simple as running:
make build
You can specify the docker registry to tag the image using the KUBE_REGISTRY environment variable. Please make sure that you use the same value in all the subsequent commands.
To push the built docker images to the registry, run:
make push
To initialize the deployment run:
(This pulls the installer images)
make init
To deploy the clusters and install the federation components, edit the
${KUBE_ROOT}/_output/federation/config.json file to describe your
clusters and run:
make deploy
To turn down the federation components and tear down the clusters run:
make destroy
Ideas for improvement
-
Continue with
destroyphase even in the face of errors.The bash script sets
set -e errexitwhich causes the script to exit at the very first error. This should be the default mode for deploying components but not for destroying/cleanup.