Closed fjogeleit closed 2 years ago
/assign @mritunjaysharma394
in my case the cronjob just hangs in the state:
kubectl describe cronjob policyreport ─╯ Name: policyreport Namespace: default Labels: <none> Annotations: <none> Schedule: 0 * * * * Concurrency Policy: Allow Suspend: False Successful Job History Limit: 3 Failed Job History Limit: 1 Starting Deadline Seconds: <unset> Selector: <unset> Parallelism: <unset> Completions: <unset> Pod Template: Labels: <none> Service Account: clusterpolicyreport Containers: policyreport: Image: mritunjay394/policyreport Port: <none> Host Port: <none> Environment: <none> Mounts: <none> Volumes: <none> Last Schedule Time: <unset> Active Jobs: <none> Events: <none>
and job is not created
at the same time, if I try to create just a pod with image image: mritunjay394/policyreport, then I also get an error invalid character 'A' looking for beginning of value
@mritunjaysharma394
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closing this issue.
On my local K3s Cluster the Jobs pending in Error state with the following logs:
Kubernetes Version: v1.21.6+k3s1