search

GoogleContainerTools / kubehost

Expose web services directly on GKE nodes during development.
Apache License 2.0
115 stars 16 forks source link

Re-binding does not copy updates made to original deployment #9

Closed ahmetb closed 5 years ago

ahmetb commented 5 years ago

(As I stated in a previous issue, I expect kubehost to not to create a new deployment OR continuously mirror changes I make to my original deployment.)

Problem

I had a deployment/service that was kubehost bind'ed before.

I scaled it up with kubectl scale deployment/hello-server --replicas=3 from 1 replica.

I didn't expect hello-server-hostport deployment to be updated automatically (because I already figured out kubehost is an imperative tool).

What was unexpected is when I run kubectl bind hello-server again, I expected hello-server-hostport deployment to be "cloned" again and have its replcias updated to 3. This didn't happen.

$ kubectl get deployments

NAME                    DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
hello-server            3         3         3            3           17m
hello-server-hostport   1         1         1            1           17m
ahmetb commented 5 years ago

I suppose I understood this wrong.

-hostport deployment isn't a clone of my deployment. It's just a gcr.io/google_containers/proxy-to-service.