Skip to content

Inserted ttl to clean old jobs #1027

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

luigi-bitonti
Copy link

No description provided.

@luigi-bitonti luigi-bitonti requested a review from a team as a code owner March 5, 2025 15:51
Copy link

hashicorp-cla-app bot commented Mar 5, 2025

CLA assistant check
All committers have signed the CLA.

@benashz
Copy link
Collaborator

benashz commented Mar 6, 2025

Hi @luigi-bitonti - from our test setup running on K8s 1.32.0, the upgrade CRDs Job seems to be reaped after completion. Are you seeing something else on your side?

Thanks,

Ben

@luigi-bitonti
Copy link
Author

luigi-bitonti commented Mar 7, 2025

Hi @benashz
Unfortunately on my cluster no. I opened an issue for the same reason on another product's repo: kyverno/kyverno#11665

I discovered by pure chance that by manually deleting the job, the upgrade goes ahead, so I tried to insert the TTL and it worked.
I also opened a Google case, but they couldn't help me either.

If you don't want the parameter to always be inserted, could we at least insert it only if the variable is valued?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants