This is creating actions.yml and config.yml in a configmap. the configmap gets mounted and then run. Since the binary is in /curator we can't mount it in there, so creating a new dir.
Expected Behavior
Curator runs, using the actions.yml and config.yml that are provided.
Actual Behavior
$ kubectl logs handtest14-xml64
Usage: curator [OPTIONS] ACTION_FILE
Try 'curator --help' for help.
Error: No such option: --config /dummy/config.yml /dummy/actions.yml
Steps to Reproduce the Problem
Create minikube cluster
deploy above yaml
create job from cronjob by hand: oc create job --from=cronjob/curator handtest1
Specifications
Version: untergeek/curator:8.0.8
Platform: MacOS / MiniKube
$ minikube version
minikube version: v1.32.0
commit: 8220a6eb95f0a4d75f7f2d7b14cef975f050512d
Additional information
When running the image locally, there are no issues like :
$ docker run -ti --rm curator-test --config /curator/config.yml /curator/actions.yml
No "elasticsearch" setting in supplied configuration. Using defaults.
No "logging" setting in supplied configuration. Using defaults.
To submit a bug or report an issue
I'm trying to run curator in a container on a kubernetes cluster.
This is creating actions.yml and config.yml in a configmap. the configmap gets mounted and then run. Since the binary is in
/curator
we can't mount it in there, so creating a new dir.Expected Behavior
Curator runs, using the actions.yml and config.yml that are provided.
Actual Behavior
Steps to Reproduce the Problem
Specifications
Additional information
When running the image locally, there are no issues like :