5621bc1ee1
Changes the key name to `SPECIAL_LEVEL` in the config map volume definition. This is consistent with the rest of the example. Otherwise, this pod does not start because there is no key with that name in the `special-config` config map. |
||
|---|---|---|
| .. | ||
| admin | ||
| application | ||
| audit | ||
| configmap | ||
| controllers | ||
| debug | ||
| federation | ||
| minikube | ||
| podpreset | ||
| pods | ||
| policy | ||
| service | ||
| windows | ||
| README.md | ||
| examples.go | ||
| examples_test.go | ||
README.md
Note: These tests are importing code from kubernetes that isn't really meant to be used outside the repo. This causes vendoring problems. As a result, we have to work around those with these lines in the travis config:
- rm $GOPATH/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery
- rm $GOPATH/src/k8s.io/kubernetes/vendor/k8s.io/apiserver
- rm $GOPATH/src/k8s.io/kubernetes/vendor/k8s.io/client-go
- cp -r $GOPATH/src/k8s.io/kubernetes/vendor/* $GOPATH/src/
- rm -rf $GOPATH/src/k8s.io/kubernetes/vendor/*
- cp -r $GOPATH/src/k8s.io/kubernetes/staging/src/* $GOPATH/src/