-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Comments
Hmm, this worked for me: In one terminal: In another: Then in a third: 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? |
I had experienced missing events also. #368 (comment) I updated to 0.7.1 and havn't see the issue since. |
This is reproducible for me too |
Also, we cannot to kubectl describe to pods pending state |
I can confirm that's also happening to me |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
|
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
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. |
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.
Is there something we need configure with minikube to get this to work?
The text was updated successfully, but these errors were encountered: