Added guide for pod-level integration with Argo Workflows

[sam-leitch-oxb]

What type of PR is this?

/kind documentation

What this PR does / why we need it:

Adds documentation on how to integrate with Argo Workflows using plain pod management.

Which issue(s) this PR fixes:

Related to #74

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Added documentation on pod-level integration with Argo Workflows.

[linux-foundation-easycla]

• ❌ - login: @sam-leitch-oxb / name: Sam Leitch . The commit (3c39267) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sam-leitch-oxb
Once this PR has been reviewed and has the lgtm label, please assign moficodes for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• site/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-sigs-kueue ready!

Name	Link
🔨 Latest commit	3c39267
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-kueue/deploys/6595db67cfcdbf0008a4141f
😎 Deploy Preview	https://deploy-preview-1545--kubernetes-sigs-kueue.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[k8s-ci-robot]

Welcome @sam-leitch-oxb!

It looks like this is your first PR to kubernetes-sigs/kueue 🎉. 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-sigs/kueue 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]

Hi @sam-leitch-oxb. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[alculquicondor]

Hi @sam-leitch-oxb, any reason why you closed this PR?

[chenxi-seu]

@alculquicondor Hi, there seems to be progressive strides towards amalgamating Argo workflow support with Kueue. I am very interested in this feature and was hoping to get some updates on its progress and any future plans. Could you please share any information about the current status or expected timelines?

[sam-leitch-oxb]

Hi @sam-leitch-oxb, any reason why you closed this PR?

Need some time to get the CLA approved (using a corporate account)
I didn't want to hold up anything in the interim.

[tenzen-y]

@alculquicondor Hi, there seems to be progressive strides towards amalgamating Argo workflow support with Kueue. I am very interested in this feature and was hoping to get some updates on its progress and any future plans. Could you please share any information about the current status or expected timelines?

@chenxi-seu You can track Argo integration at argoproj/argo-workflows#12363 and #74.

[agilgur5]

Nice guide, this is helpful!

I couldn't comment on the PR in-line as the fork was deleted (GH was throwing an error), so a comment below:

For the very last line: Did you mean plugin instead of resource?
http and plugin actually do create Pods, it's just not documented much (I found this out only after being a contributor for many months. it's very vaguely mentioned in the http template docs and manifests linked therein). They create an agent Pod if one does not exist in the Workflow's namespace. If one already exists, it gets re-used.