Skip to content
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

No watch events are generated using minikube #489

Closed
dcheese opened this issue Aug 15, 2016 · 10 comments
Closed

No watch events are generated using minikube #489

dcheese opened this issue Aug 15, 2016 · 10 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@dcheese
Copy link

dcheese commented Aug 15, 2016

When using minikube, we are not able receive pod change events when providing the watch parameter. It just hangs, with no response. It does work when we try try to curl against a full kubernetes server/installation.

kubctl proxy &
curl http://localhost:8001/api/v1/pods?watch=true

Is there something we need configure with minikube to get this to work?

@dlorenc
Copy link
Contributor

dlorenc commented Aug 15, 2016

Hmm, this worked for me:

In one terminal:
$ kubectl proxy

In another:
$ curl http://localhost:8001/api/v1/pods?watch=true

Then in a third:
$ kubectl create -f busybox.yaml

Where busybox.yaml is:

apiVersion: v1
kind: Pod
metadata:
  name: busybox
spec:
  containers:
  - image: gcr.io/dlorenc-vmtest4/foo
    command:
      - sleep
      - "3600"
    imagePullPolicy: IfNotPresent
    name: busybox
  imagePullSecrets:
  - name: secret.json
  restartPolicy: Always

I see output in the curl terminal.

So this should work out of the box in minikube. Do you see anything running in Minikube with kubectl get pods --all-namespaces?

@andrewgdavis
Copy link

I had experienced missing events also. #368 (comment)

I updated to 0.7.1 and havn't see the issue since.

@dlorenc dlorenc added the kind/bug Categorizes issue or PR as related to a bug. label Aug 18, 2016
@hsaputra
Copy link

This is reproducible for me too

@hsaputra
Copy link

Also, we cannot to kubectl describe to pods pending state

@erez-rabih
Copy link

I can confirm that's also happening to me
minikube version: v0.19.0

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 30, 2017
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 29, 2018
@hsaputra
Copy link

/remove-lifecycle rotten

@fejta-bot
Copy link

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

@msidler1701
Copy link

msidler1701 commented Mar 14, 2018

dlorenc's example above worked great for me. The only change was I pasted the "http://localhost:8001/api/v1/pods?watch=true" in a browser...curl didn't show anything. In the browser it was continously updating. All this was with Minikube running. Attached is a sample events output. Rename to JSON extension as you can't copy a .json file here.
K8s-events.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

8 participants