New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

phase out cluster/ directory #49213

Open
mikedanese opened this Issue Jul 19, 2017 · 31 comments

Comments

Projects
None yet
@mikedanese
Member

mikedanese commented Jul 19, 2017

sig-cluster-lifecycle has decided to phase out the cluster/ directory over the next couple releases in favor of deployment automations maintained outside of the core repo and outside of kubernetes orgs.

@kubernetes/sig-cluster-lifecycle-misc

k8s-merge-robot added a commit that referenced this issue Jul 20, 2017

Merge pull request #49148 from mikedanese/deprecate-cluster
Automatic merge from submit-queue (batch tested with PRs 48377, 48940, 49144, 49062, 49148)

add some more deprecation warnings to cluster

Part of #49213
@kubernetes/sig-cluster-lifecycle-misc
@madhusudancs

This comment has been minimized.

Contributor

madhusudancs commented Jul 20, 2017

cc @kubernetes/sig-federation-misc

@madhusudancs

This comment has been minimized.

Contributor

madhusudancs commented Jul 20, 2017

This affects federation. Federation test infra depends on cluster/ right now. What's the recommended solution for cloud resource provisioning? It's kubeadm for cluster turn up, I believe?

@roberthbailey

This comment has been minimized.

Member

roberthbailey commented Jul 20, 2017

What kind of resource provisioning are you thinking of? kubeadm is designed to run on machines that are pre-provisioned. For e2e tests of kubeadm we are currently using kubernetes-anywhere (which uses terraform) to create the VMs on which to run tests.

@csbell

This comment has been minimized.

Contributor

csbell commented Jul 20, 2017

@madhusudancs

This comment has been minimized.

Contributor

madhusudancs commented Jul 20, 2017

What kind of resource provisioning are you thinking of?

VMs, network, etc. We just need kubernetes clusters running on GCE like most other kubernetes tests would need, with an exception that we need multiple clusters instead of one and some additional network configuration. It has been a while since I last tried kubernetes-anywhere, so may be that's an alternative worth evaluating.

The dependency seems to be mostly on some of the cluster bash lib utilities (cluster/lib/logging.sh) and some wrappers kubectl.sh. Copying the relevant bits to federation/cluster/common.sh might be workable.

Federation tests are entirely built on top kube-{up,down}.sh. They also use cluster/lib. But it depends on pretty much everything that's related to kube-up.

@luxas

This comment has been minimized.

Member

luxas commented Jul 21, 2017

@madhusudancs I'd love to see if we can get federation e2e's working smoothly on top of kubeadm e2e clusters.

The only thing that would be a hard limit is spawning two or more clusters, right?
Then we'd be running kubefed init --args and something like e2e.test --ginkgo.focus="Federation" and it should work?

@madhusudancs

This comment has been minimized.

Contributor

madhusudancs commented Jul 21, 2017

@luxas at a high level, yes. There are some intricate details. For example, clusters must use different CIDRs for pod addresses, they should be in different zones, etc. But those details could be worked out and shouldn't be hard. And spawning multiple clusters shouldn't be difficult as well. They could be separate, possibly parallel, invocations of kubeadm.

@luxas

This comment has been minimized.

Member

luxas commented Jul 25, 2017

@madhusudancs Yeah, I think it should be pretty straightforward as long as one knows how to create VMs on GCE :)

Would you like to join our SIG call later today to spec out details?

@madhusudancs

This comment has been minimized.

Contributor

madhusudancs commented Jul 25, 2017

@luxas I am already too late for today's meeting. I cannot join the meeting next week and the week following that because it overlaps with SIG-Federation meetings. May be in 3 weeks from now, if you can put it on the agenda?

@madhusudancs

This comment has been minimized.

Contributor

madhusudancs commented Jul 25, 2017

Also cc @shashidharatd who is interested in this.

@luxas

This comment has been minimized.

Member

luxas commented Jul 26, 2017

@madhusudancs We have a meeting on Friday 9 PT if that works for you as well

@irfanurrehman

This comment has been minimized.

Member

irfanurrehman commented Jul 27, 2017

@luxas, I am also interested in this effort. Is the link posted on the community page for sig-cluster-lifecycle the meeting link to join?
@madhusudancs @shashidharatd can we consolidate this effort (may be post this meeting, or some other time) to address this and similar discussion from our last federation sig meeting also.

@madhusudancs

This comment has been minimized.

Contributor

madhusudancs commented Jul 28, 2017

@luxas I can't make it to the meeting tomorrow too. How about we put this on the agenda for 08/04 or 08/15?

@irfanurrehman @shashidharatd feel free to go if you can tomorrow.

@madhusudancs @shashidharatd can we consolidate this effort (may be post this meeting, or some other time) to address this and similar discussion from our last federation sig meeting also.

Sure.

@luxas

This comment has been minimized.

Member

luxas commented Jul 31, 2017

How about we put this on the agenda for 08/04 or 08/15?

@madhusudancs You mean the sig-cluster-lifecycle calls on those dates, right?

@madhusudancs

This comment has been minimized.

Contributor

madhusudancs commented Jul 31, 2017

@luxas yeah.

@bgrant0607

This comment has been minimized.

Member

bgrant0607 commented Aug 22, 2017

Ref #24343

@urzds

This comment has been minimized.

urzds commented Oct 17, 2017

If the openstack-heat provider for kube-up is now deprecated: What is the currently recommended method to setup Kubernetes on OpenStack?

/cc @magreiner

k8s-merge-robot added a commit that referenced this issue Jan 13, 2018

Merge pull request #58246 from mikedanese/rm-kube-push
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

cluster: remove kube-push

see #49213

```release-note
Remove deprecated kube-push.sh functionality. 
```

k8s-merge-robot added a commit that referenced this issue Jan 13, 2018

Merge pull request #58247 from mikedanese/rm-cvm
Automatic merge from submit-queue (batch tested with PRs 58246, 58247). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

cluster: remove support for cvm from gce kube-up

see #49213


```release-note
Remove deprecated ContainerVM support from GCE kube-up. 
```

k8s-merge-robot added a commit that referenced this issue Jan 14, 2018

Merge pull request #58250 from mikedanese/rm-lib
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

cluster: move logging library to hack/

it's used once in cluster and used a bunch in hack/ and build/

see #49213
```release-note
NONE
```

k8s-merge-robot added a commit that referenced this issue Jan 17, 2018

Merge pull request #58248 from mikedanese/rm-salt
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

cluster: remove salt

Nothing uses it directly. There were some dangling dependencies from GCE and Centos kube-ups, so I just copied them into respective dirs.

see #49213

```release-note
Remove deprecated and unmaintained salt support. kubernetes-salt.tar.gz will no longer be published in the release tarball.
```

k8s-merge-robot added a commit that referenced this issue Jan 23, 2018

Merge pull request #58658 from roberthbailey/fluentd-gcp
Automatic merge from submit-queue (batch tested with PRs 58697, 58658, 58676, 58674). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

Remove salt configuration from the fluentd-gcp configuration.

Remove a bit of left-over salt. This was missed in #58248

xref: #49213

**Release note**:

```release-note
NONE
```

k8s-merge-robot added a commit that referenced this issue Feb 3, 2018

Merge pull request #58564 from mikedanese/rm-opencontrail
Automatic merge from submit-queue (batch tested with PRs 55439, 58564, 59028, 59169, 59259). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

cluster: delete lot's of stuff

let me know if any of this is too aggressive. 

see #49213

```release-note
Remove unmaintained kube-registry-proxy support from gce kube-up.
```

k8s-merge-robot added a commit that referenced this issue Feb 17, 2018

Merge pull request #59908 from roberthbailey/kube-up-refactoring
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

Move code only used by gce out of common.sh and into gce/util.sh

xref #49213

**Special notes for your reviewer**:

**Release note**:

```release-note
NONE
```
@fejta-bot

This comment has been minimized.

fejta-bot commented Apr 9, 2018

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

gregory-m added a commit to gregory-m/kubernetes that referenced this issue May 22, 2018

gregory-m added a commit to gregory-m/kubernetes that referenced this issue May 22, 2018

remove deprecated openstack heat
this directory hasn't been touched in a year.

see kubernetes#49213

gregory-m added a commit to gregory-m/kubernetes that referenced this issue May 22, 2018

@fejta-bot

This comment has been minimized.

fejta-bot commented Jul 8, 2018

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

This comment has been minimized.

fejta-bot commented Oct 9, 2018

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

@cblecker

This comment has been minimized.

Member

cblecker commented Oct 9, 2018

/remove-lifecycle stale

@mikedanese

This comment has been minimized.

Member

mikedanese commented Nov 7, 2018

Various non-critical addons have been pretty noisy in the vulnscans. Unfortunately many of our e2e tests currently depend on them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment