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
Fix name for Pods of NonIndexed Jobs #105676
Conversation
/triage accepted |
Change-Id: I0ea4685a82f4cdec0caab362d52144476652f95a
c6031ff
to
4ef9d18
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alculquicondor, soltysh The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What would it take to get this backported to the next 1.22.x release? This is causing pod creation failure with certain job names as seen here. |
Oh, please create a cherry-pick https://github.com/kubernetes/community/blob/master/contributors/devel/sig-release/cherry-picks.md |
In our effort to support all K8s versions, we found a small fix on our side to work with this issue, so it can wait for 1.23 from my perspective. |
Sg, I'm happy to lgtm if you send the cherry-pick |
…y-pick-of-#105676-upstream-release-1.22 Automated cherry pick of #105676: Fix name for Pods of NonIndexed Jobs
What type of PR is this?
/kind bug
/kind regression
What this PR does / why we need it:
Removes generate name from NonIndexed Jobs. Otherwise, the name has the form:
job-name--1-
where
-1
comes from the invalid completion index.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
This was accidentally added in #101601. I'm pretty sure this is just a cosmetic issue: pods would still be created because podGenerateNameWithIndex already truncates the names to fit the pod name limits.
Does this PR introduce a user-facing change?