Update jobs-run-to-completion.md - fix numbering

[borod108]

seems to me it should be 1,2,3 and not 1,1,1 :)

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[k8s-ci-robot]

Welcome @borod108!

It looks like this is your first PR to kubernetes/website 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/website has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign zacharysarah
You can assign the PR to them by writing /assign @zacharysarah in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• content/en/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

Deploy preview for kubernetes-io-master-staging ready!

Built with commit ece5eb0

https://deploy-preview-21177--kubernetes-io-master-staging.netlify.app

[borod108]

I signed it

[sftim]

It seems to me that the original numbering is valid Markdown, but the bullets aren't being parsed right.
The reason for leaving all the numbers as 1. is that it makes future editing easier as list items are removed or added.

My suggestion for how this part of the page should look as Markdown source:

1. Non-parallel Jobs
   * normally, only one Pod is started, unless the Pod fails.
   * the Job is complete as soon as its Pod terminates successfully.
1. Parallel Jobs with a *fixed completion count*:
   * specify a non-zero positive value for `.spec.completions`.
   * the Job represents the overall task, and is complete when there is one successful Pod for each value in the range 1 to `.spec.completions`.
   * **not implemented yet:** Each Pod is passed a different index in the range 1 to `.spec.completions`.
1. Parallel Jobs with a *work queue*:
   * do not specify `.spec.completions`, default to `.spec.parallelism`.
   * the Pods must coordinate amongst themselves or an external service to determine what each should work on. For example, a Pod might fetch a batch of up to N items from the work queue.
   * each Pod is independently capable of determining whether or not all its peers are done, and thus that the entire Job is done.
   * when _any_ Pod from the Job terminates with success, no new Pods are created.
   * once at least one Pod has terminated with success and all Pods are terminated, then the Job is completed with success.
   * once any Pod has exited with success, no other Pod should still be doing any work for this task or writing any output.  They should all be in the process of exiting.

What do you think about that approach, @borod108 ?

[borod108]

@sftim than you for your quick review! How will the end user see it then?

[sftim]

You can preview your changes locally, or push them and view the Netlify preview:
https://deploy-preview-21177--kubernetes-io-master-staging.netlify.app/docs/concepts/workloads/controllers/jobs-run-to-completion/

Do either of those help?

[sftim]

@borod108 did you get time to preview these changes?

[sftim]

This is trying to fix a regression that's related to issue #20335

[jimangel]

Thanks for the PR @borod108! However, a PR has already been merged that fixes the issue: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/

Thanks again!
/close

[k8s-ci-robot]

@borod108: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

@jimangel: Closed this PR.

In response to this:

Thanks for the PR @borod108! However, a PR has already been merged that fixes the issue: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/

Thanks again!
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.