Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Usage of kubernetes deprecated cronjob API when newer APIs are present #1553

Closed
banjoh opened this issue May 30, 2024 · 0 comments · Fixed by #1554
Closed

Usage of kubernetes deprecated cronjob API when newer APIs are present #1553

banjoh opened this issue May 30, 2024 · 0 comments · Fixed by #1554

Comments

@banjoh
Copy link
Member

banjoh commented May 30, 2024

Bug Description

The cluster resources collector checks for newer versions of cronjobs API, but that logic does not seem to work as expected. The old batch/v1beta1/cronjobs is still used

Expected Behavior

The implementation should use batch/v1/cronjobs APIs

Steps To Reproduce

  • Use the spec below to collect a support bundle from a 1.29 or newer k8s cluster
cat <<EOF | support-bundle -v=10 -
apiVersion: troubleshoot.sh/v1beta2
kind: SupportBundle
spec: {}
EOF
  • Grep cronjobs from the logs and notice references of batch/v1beta1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant