Open srfrnk opened 6 years ago
Option 1 is currently possible by setting a new server IP ks env set dev --server=https://$(minikube ip):8443
assuming namespace, ports stay the same (but those are also configurable)
Can't do much about option 3. Option 2 sounds interesting but unlikely to happen imo
Thanx. That's a nice workaround. Would be better if this could be embedded into App.yaml instead so you would't have to run an extra cmd every time.
I agree, it woud be useful to have support in ksonnet for getting the minikube URL automatically.
/kind feature
What happened: Using ksonnet with minikube. Created an evironment called 'dev'. The
./app.yaml
file containsserver: https://192.168.39.117:8443
but this IP changes when minikube is restarted.What you expected to happen: Possible solutions: 1) Having a configurable IP for the
app.yaml
environment e.g. from environment variable that could be set up usingminikube ip
1) Having a specialks env
to specify a minikube env that would dynamically useminikube ip
1) Having minikube get a cmd line arg with IP to use (currently not supported - can't tell if it will - see 1 2 3)How to reproduce it (as minimally and precisely as possible):
ksonnet will not be able to connect to server.
Anything else we need to know?:
Environment:
ksonnet version (use
ks version
): ksonnet version: 0.12.0 jsonnet version: v0.11.2 client-go version: kubernetes-1.10.4Kubernetes version (use
kubectl version
): Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-09T18:02:47Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:44:10Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}