deploy from kuberentes source (KPATH)

[jayunit100]

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

This is a Feature request.

We need to be able to deploy from source, i.e. minikube --build=$KPATH or something, for dev/testing.

As of now im not 100% sure, but minikube appears to be decoupled from source, maybe its pulling releases down from somewhere external?

[whitlockjc]

Has there been any movement on this? I would love to help out as running development builds of Kubernetes on Mac has proven impossible. Since minikube is the future for running Kubernetes locally, this seems like a better approach than hacking hack/local-up-cluster.sh like I've tried here.

[r2d4]

There is some work to run local e2e tests with minikube upstream on kubernetes/kubernetes

kubernetes/kubernetes#38975

[MHBauer]

Since, kubernetes/kubernetes#38975 was closed, should we make an effort to get localkube into the core as it's own thing? The ability to specify localkube is a good start, and if I can generate localkube myself, that would be an amazing start to deploying a customized version at will.

Is there another way to get an updated/current with source localkube? An easy way to build localkube by specifying a code path?

[dlorenc]

Once we land kubeadm support you'll be able to deploy from a kubeadm built from a kpath.

[fejta-bot]

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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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]

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
/remove-lifecycle stale

[fejta-bot]

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