search

kubernetes-retired / kubeadm-dind-cluster

[EOL] A Kubernetes multi-node test cluster based on kubeadm
Apache License 2.0
1.11k stars 274 forks source link

stable release tags #195

Closed gregwebs closed 5 years ago

gregwebs commented 6 years ago

This is a great project, and I am glad there is a lot of development on it to push it forward. But it seems that there is a fair amount of instability on master right now. It would be very helpful to have some release tags to use for installing. I am creating a tutorial that requires a multi-node Kubernetes install. Running kubeadm-dind-cluster is recommended, but now I don't know what commit I should be recommending.

jellonek commented 6 years ago

I agree on that this should be done soon. For this moment I would suggest to use https://github.com/kubernetes-sigs/kubeadm-dind-cluster/commit/64a2befa65ce23475158b65793e56d4bc1ae0a79 as a latest stable commit.

gregwebs commented 6 years ago

Thanks! I have local volume mounting issues on that commit that I don't see on our fork. I haven't tracked down where the issue diverges yet.

Error: failed to start container "tidb-operator": Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "process_linux.go:359: container init caused \"rootfs_linux.go:54: mounting \\\"/etc/localtime\\\" to rootfs \\\"/dind/docker/overlay2/acd1036e479c09a05eb76450dc0ba58ade6e5c2f0d1eff48b4729880d648e421/merged\\\" at \\\"/dind/docker/overlay2/acd1036e479c09a05eb76450dc0ba58ade6e5c2f0d1eff48b4729880d648e421/merged/etc/localtime\\\" caused \\\"not a directory\\\"\""
pigmej commented 6 years ago

What about https://github.com/kubernetes-sigs/kubeadm-dind-cluster/blob/master/fixed/dind-cluster-stable.sh ? That's the current "sub-optimal" way. (per discussion: https://github.com/kubernetes-sigs/kubeadm-dind-cluster/issues/115)

@ivan4th is currently working on containerizing "core" scripts, and leaving just "frontend" to end user, that should fix your problem definitely.

gregwebs commented 6 years ago

Great!

fejta-bot commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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

k8s-ci-robot commented 5 years ago

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/kubeadm-dind-cluster/issues/195#issuecomment-504863484): >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](https://github.com/fejta). >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.