Skip to content
This repository has been archived by the owner on Apr 8, 2022. It is now read-only.

CrashLoopBackOff when resourcesToWatch.pod is false or not set #73

Open
vdboor opened this issue Jan 5, 2018 · 3 comments
Open

CrashLoopBackOff when resourcesToWatch.pod is false or not set #73

vdboor opened this issue Jan 5, 2018 · 3 comments

Comments

@vdboor
Copy link
Contributor

vdboor commented Jan 5, 2018

When the resourcesToWatch is an empty dictionary, or the pod setting is omitted, kubewatch crashes on startup. While this seems like a minor issue, the default incubator helm chart follows this same pattern!

I've worked around this by adding resourcesToWatch to the improved README (#72), but it seems useful to have a proper solution out of the box.

@vdboor vdboor changed the title CrashLoopBackOff when resourcesToWatch.pod is false CrashLoopBackOff when resourcesToWatch.pod is false or not set Jan 5, 2018
vdboor added a commit to vdboor/charts that referenced this issue Jan 5, 2018
…h config

It also makes the default configuration easier to discover

CC vmware-archive/kubewatch#73
@vdboor
Copy link
Contributor Author

vdboor commented Jan 5, 2018

I've created a PR for the helm chart here: helm/charts#3241

@sebgoa
Copy link
Contributor

sebgoa commented Jan 5, 2018

thanks, we will review the PR for the chart.

@vdboor
Copy link
Contributor Author

vdboor commented Jan 8, 2018

thanks! :-)

I've also noticed that setting resourcesToWatch.pod to false crashes kubewatch. That might be worth looking into.

k8s-ci-robot pushed a commit to helm/charts that referenced this issue Jan 14, 2018
…h config (#3241)

It also makes the default configuration easier to discover

CC vmware-archive/kubewatch#73
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants