Kops: offline cluster creation

Created on 2 Nov 2018 · 9Comments · Source: kubernetes/kops

It would be really handy to do have a '--offline' flag to the create, update, and rolling-update commands, with the goal being the ability to deploy kubernetes via kops on offline cloud-providers like, isolated openstack, isolated vsphere, aws-govcloud...

Maybe this could be accomplished by kops expecting the required binaries to be in the current working directory and throwing an error if something is missing, like a package dependency check.
My current work-around is to identify all the binaries and docker images required to build via terraform and kops, host them in a local nexus repository.

So far I have identified the following as necessary to build the master and worker nodes via kops --target terraform.
https://kubeupv2.s3.amazonaws.com/kops/1.10.0/linux/amd64/nodeup
https://storage.googleapis.com/kubernetes-release/release/v1.10.6/bin/linux/amd64/kubelet
https://storage.googleapis.com/kubernetes-release/release/v1.10.6/bin/linux/amd64/kubectl
https://storage.googleapis.com/kubernetes-release/network-plugins/cni-plugins-amd64-v0.6.0.tgz
https://kubeupv2.s3.amazonaws.com/kops/1.10.0/linux/amd64/utils.tar.gz
https://kubeupv2.s3.amazonaws.com/kops/1.10.0/images/protokube.tar.gz

and I have identified these docker images as part of the full kops config
k8s.gcr.io/etcd:2.2.1
k8s.gcr.io/kube-apiserver:v1.10.6
k8s.gcr.io/kube-controller-manager:v1.10.6
k8s.gcr.io/kube-proxy:v1.10.6
k8s.gcr.io/kube-scheduler:v1.10.6
k8s.gcr.io/pause-amd64:3.0

lifecyclrotten

Source

sdfaz

👍2

Most helpful comment

bump

mward29 on 18 Sep 2019

👍3

All 9 comments

Any news?

abdennour on 10 Dec 2018

Any update I am looking to do a complete offline install as well. For example all executables in S3 and those docker containers in a private registry. I know there is the mirror docker setting but does that apply to these images in the userdata as well?

rwd5213 on 3 Mar 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 1 Jun 2019

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 1 Jul 2019

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 31 Jul 2019

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.