Remove the deprecated vagrant kube-up implementation.

kubernetes · Jan 11, 2018 · 8d44e0b · 8d44e0b
1 parent 98277ff
commit 8d44e0b
Show file tree

Hide file tree

Showing 16 changed files with 5 additions and 1,594 deletions.
diff --git a/Vagrantfile b/Vagrantfile
diff --git a/build/lib/release.sh b/build/lib/release.sh
@@ -517,7 +517,6 @@ EOF
   cp -R "${KUBE_ROOT}/docs" "${release_stage}/"
   cp "${KUBE_ROOT}/README.md" "${release_stage}/"
   cp "${KUBE_ROOT}/Godeps/LICENSES" "${release_stage}/"
-  cp "${KUBE_ROOT}/Vagrantfile" "${release_stage}/"
 
   echo "${KUBE_GIT_VERSION}" > "${release_stage}/version"
 

diff --git a/build/release-tars/BUILD b/build/release-tars/BUILD
@@ -193,7 +193,6 @@ pkg_tar(
     files = [
         "//:Godeps/LICENSES",
         "//:README.md",
-        "//:Vagrantfile",
         "//:version",
         "//cluster:all-srcs",
         "//docs:all-srcs",

diff --git a/cluster/saltbase/README.md b/cluster/saltbase/README.md
@@ -4,11 +4,10 @@ This is the root of the SaltStack configuration for Kubernetes. A high
 level overview for the Kubernetes SaltStack configuration can be found [in the docs tree.](https://kubernetes.io/docs/admin/salt/)
 
 This SaltStack configuration currently applies to default
-configurations for Debian-on-GCE, Fedora-on-Vagrant, Ubuntu-on-AWS and
-Ubuntu-on-Azure. (That doesn't mean it can't be made to apply to an
-arbitrary configuration, but those are only the in-tree OS/IaaS
-combinations supported today.) As you peruse the configuration, these
-are shorthanded as `gce`, `vagrant`, `aws`, `azure-legacy` in `grains.cloud`;
+configurations for Debian-on-GCE. (That doesn't mean it can't
+be made to apply to an arbitrary configuration, but those are
+only the in-tree OS/IaaS combinations supported today.) As you
+peruse the configuration, this is shorthanded as `gce`,  in `grains.cloud`;
 the documentation in this tree uses this same shorthand for convenience.
 
 See more:

diff --git a/cluster/vagrant/OWNERS b/cluster/vagrant/OWNERS