Fix controller crash caused by glog attempting to write to /tmp #94
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves: #85
We were using a
k8s.io/apimachinery
version which somehow was using glog where it did not honor thelogtostderr
flag in glog. This caused the controller to log to/tmp
in certain cases, which crashed the controller since /tmp does not exist in scratch containers.This change also allows a dev version of the controller image, for much faster docker builds: