Unable to deploy a job
juandspy opened this issue · comments
Context
I'm trying to deploy a job with bonfire and Clowder to an ephemeral cluster. Here is the configuration:
- clowdapp.yaml
test.yaml:
appsFile:
host: gitlab
repo: insights-platform/cicd-common
path: bonfire_configs/ephemeral_apps.yaml
apps:
- name: ccx-data-pipeline
components:
- name: insights-results-aggregator-exporter
host: github
repo: RedHatInsights/insights-results-aggregator-exporter
path: deploy/clowdapp.yaml
ref: CCXDEV-5895
parameters:
CLOWDER_ENABLED: "true"
IMAGE_TAG: latest
- name: ccx-insights-results
host: github
repo: RedHatInsights/insights-results-aggregator
path: deploy/clowdapp.yaml
ref: master
parameters:
CLOWDER_ENABLED: "true"
CLOUDWATCH_ENABLED: "false"
IMAGE_TAG: qa- commands:
ns=$(bonfire namespace reserve)
bonfire deploy -c test.yaml -n $ns ccx-data-pipeline
Results
Running oc get jobs -n $ns returns "No resources found".
Extra information
If I set a schedule it works.
Questions
- Are jobs supported? Or only cronjobs?
- Is this a problem of
bonfire? - Is my
clowdapp.yamlbadly configured?
Thanks in advance.
Based on what I am seeing in your clowdapp.yaml, you're deploying a ClowdApp with a job configuration.
In order to invoke that job, you'd need to apply a ClowdJobInvocation resource into your namespace. Once clowder sees that invocation request, it would spin up a Job for your app.
To clarify, if you had a plain Job resource in your template, bonfire would deploy it.
But what you have is a ClowdApp with jobs defined in its spec. Those require a ClowdJobInvocation to actually fire the job.
Oh, thanks a lot. That woks. For cronjobs is not necessary to use a CJI, right?