Skip to content

error: unable to recognize batch/v2alpha1 #38

Open
@jgbolger

Description

@jgbolger

Hi,

I'm trying to install on minishift (Windows 10) and I am getting the following error:
error: unable to recognize batch/v2alpha1, Kind=CronJob: no matches for kind "CronJob" in version "batch/v2alpha1"

+ oc process -f template.yml INVOKER_MEMORY_REQUEST=512Mi INVOKER_MEMORY_LIMIT=512Mi INVOKER_JAVA_OPTS=-Xmx256m INVOKER_MAX_CONTAINERS=2 COUCHDB_MEMORY_REQUEST=256Mi COUCHDB_MEMORY_LIMIT=256Mi
+ oc create -f -
configmap "whisk.config" created
configmap "whisk.limits" created
configmap "whisk.runtimes" created
configmap "strimzi-openwhisk" created
service "controller" created
configmap "controller.config" created
statefulset.apps "controller" created
job.batch "install-catalog" created
service "couchdb" created
service "couchdb-headless" created
configmap "db.config" created
statefulset.apps "couchdb" created
configmap "invoker.config" created
configmap "invoker" created
serviceaccount "openwhisk" created
rolebinding.authorization.openshift.io "openwhisk" created
statefulset.apps "invoker" created
job.batch "preload-openwhisk-runtimes" created
service "nginx" created
route.route.openshift.io "openwhisk" created
configmap "nginx" created
deployment.extensions "nginx" created
secret "whisk.auth" created
secret "db.auth" created
deployment.extensions "strimzi-cluster-controller" created
configmap "alarmprovider" created
deployment.extensions "alarmprovider" created
error: unable to recognize batch/v2alpha1, Kind=CronJob: no matches for kind "CronJob" in version "batch/v2alpha1"
+ ./bin/wait_for_openwhisk.sh

My version info is as follows:

minishift v1.23.0+91235ee
oc v3.10.0+dd10d17
kubernetes v1.10.0+b81c8f8
features: Basic-Auth
Server https://192.168.99.100:8443
openshift v3.10.0+8e19bad-29
kubernetes v1.10.0+b81c8f8

When I run oc api-versions, I can see:

$ oc api-versions
admissionregistration.k8s.io/v1beta1
apiextensions.k8s.io/v1beta1
apiregistration.k8s.io/v1
apiregistration.k8s.io/v1beta1
apps.openshift.io/v1
apps/v1
apps/v1beta1
apps/v1beta2
authentication.k8s.io/v1
authentication.k8s.io/v1beta1
authorization.k8s.io/v1
authorization.k8s.io/v1beta1
authorization.openshift.io/v1
autoscaling/v1
autoscaling/v2beta1
batch/v1
batch/v1beta1
build.openshift.io/v1
certificates.k8s.io/v1beta1
events.k8s.io/v1beta1
extensions/v1beta1
image.openshift.io/v1
network.openshift.io/v1
networking.k8s.io/v1
oauth.openshift.io/v1
policy/v1beta1
project.openshift.io/v1
quota.openshift.io/v1
rbac.authorization.k8s.io/v1
rbac.authorization.k8s.io/v1beta1
route.openshift.io/v1
security.openshift.io/v1
storage.k8s.io/v1
storage.k8s.io/v1beta1
template.openshift.io/v1
user.openshift.io/v1
v1
webconsole.operator.openshift.io/v1alpha1

I've read on stackoverflow about the need to enable this feature via the runtime-config for kubectl. However I'm new to Kubernetes & Openshift so unsure of how this is set via Openshift.

https://stackoverflow.com/questions/45580361/kubernetes-cronjob-needs-to-set-a-runtime-config-of-batch-v2alpha1-true

Any help is much appreciated.

Regards,
John

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions