You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm new to kubernetes and I was trying to schedule the synchronisation using kubectl. However, I think I've found a bug in config file k8s-job.yaml.
After running in a terminal: "% kubectl apply -f k8s-job.yaml"
It threw the error: "error: resource mapping not found for name: "withings-garmin-sync" namespace: "" from "k8s-job.yaml": no matches for kind "CronJob" in version "batch/v1beta1" ensure CRDs are installed first"
I fixed it by changing Cronjob kind in the yaml script:
from: "apiVersion: batch/v1beta1" -> to: "apiVersion: batch/v1"
It passed through resulting in: cronjob.batch/withings-garmin-sync created
The text was updated successfully, but these errors were encountered:
Hi, I'm new to kubernetes and I was trying to schedule the synchronisation using kubectl. However, I think I've found a bug in config file k8s-job.yaml.
After running in a terminal: "% kubectl apply -f k8s-job.yaml"
It threw the error: "error: resource mapping not found for name: "withings-garmin-sync" namespace: "" from "k8s-job.yaml": no matches for kind "CronJob" in version "batch/v1beta1" ensure CRDs are installed first"
I fixed it by changing Cronjob kind in the yaml script:
from: "apiVersion: batch/v1beta1" -> to: "apiVersion: batch/v1"
It passed through resulting in: cronjob.batch/withings-garmin-sync created
The text was updated successfully, but these errors were encountered: