Skip to content

Conversation

pacoxu
Copy link
Member

@pacoxu pacoxu commented Jul 15, 2025

@riaankleinhans riaankleinhans changed the title [WIP] init CNCF TAG Workloads Foundation charts [WIP] init CNCF TAG Workloads Foundation charter Jul 29, 2025
@pacoxu pacoxu changed the title [WIP] init CNCF TAG Workloads Foundation charter init CNCF TAG Workloads Foundation charter Jul 31, 2025
@pacoxu pacoxu requested a review from kad July 31, 2025 08:16
@pacoxu
Copy link
Member Author

pacoxu commented Jul 31, 2025

cc @cncf/tag-workloads-foundation-leads

@pacoxu
Copy link
Member Author

pacoxu commented Aug 5, 2025

cc @cncf/tag-workloads-foundation-leads

I just realize that this team does not include tech leads. Hope to complete this by the end of the week or early next week.

cc @kerthcet @rajaskakodkar @srust @RainbowMango @kad

@RainbowMango
Copy link

Thanks for the reminder, just sent the request~

pacoxu and others added 2 commits August 7, 2025 10:27
@terrytangyuan terrytangyuan changed the title init CNCF TAG Workloads Foundation charter Initial CNCF TAG Workloads Foundation charter Aug 7, 2025
@pacoxu pacoxu requested review from terrytangyuan, RainbowMango and a team August 7, 2025 07:02
@pacoxu
Copy link
Member Author

pacoxu commented Aug 8, 2025

The current scope are too brief. Should we add some explanations and examples(repo or feature name) for each scope?

@RainbowMango
Copy link

The current scope are too brief. Should we add some explanations and examples(repo or feature name) for each scope?

Yeah, that'd be great! Having a brief explanation as well as some example projects would help people understand the scope correctly.

@pacoxu pacoxu requested a review from a team as a code owner August 11, 2025 08:23
@pacoxu
Copy link
Member Author

pacoxu commented Aug 11, 2025

The current scope are too brief. Should we add some explanations and examples(repo or feature name) for each scope?>
Yeah, that'd be great! Having a brief explanation as well as some example projects would help people understand the

Some items are too obvious to add more explanations, but some example projects are helpful. Added some.

Comment on lines 11 to 23
- Containers (e.g. Podman, buildpacks, etc.)
- OS
- Container Runtime(e.g. containerd, CRI-O, Kata, etc.)
- Virtual Machines (e.g. KubeVirt, Firecracker, etc.)
- Serverless (e.g. Knative, etc.)
- Web Assembly (e.g. WasmEdge, etc.)
- Batch (e.g. Kueue, JobSet, KJob, etc. )
- Serving (e.g. KServe, Gateway API Inference Extension etc.)
- Scheduling (e.g. Volcano, HAMi, etc.)
- Orchestrator (e.g. Kubernetes, Karmada, Argo Workflows, etc.)
- Deployment (e.g. Helm, kustomize, etc.)
- Dynamic Scaling (e.g. KEDA, Karpenter, Cluster Autoscaler, etc.)
- CI/CD (e.g. Argo CD, Flux, etc.)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Quick question, is it expected that a new cncf project trying to update any line of this part just to add a new example?

I guest not, so maybe remove the examples here, or replace with some non-project brand specific description.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall, I don’t think examples are necessary, except in a few cases where the category is broad or the meaning overlaps with another. But specific description may be augable, due to the scope can be tighter or looser.

So I removed those examples. Anyway, the discussions in this PR may also help other understand the scope.

This TAG covers the following sub-domains and topics within its scope:

- Containers (e.g. Podman, buildpacks, etc.)
- OS
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some background of the OS: the operating system here is more focused on special purpose operating system, e.g. container OSs, that were designed to run well defined workloads with minimal boilerplate of dependencies suited for niche use cases.
Ref: #1154

Copy link
Contributor

@srust srust left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks straight forward and simple, which is great. I added a few clarifying comments for the Scope section, but otherwise this looks good.

Thank you!

Copy link
Member

@terrytangyuan terrytangyuan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks!

@pacoxu
Copy link
Member Author

pacoxu commented Aug 20, 2025

/cc @cncf/tag-workloads-foundation-leads /assign @kevin-wangzefeng @chira001 @riaankleinhans

Kindly Ping. Do you have time to take a look again? Then we can announce our community meeting soon.

@chira001
Copy link
Contributor

LGTM - thank you for incorporating the feedback!

Copy link
Member

@kevin-wangzefeng kevin-wangzefeng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, Thanks

@pacoxu pacoxu merged commit 52c8e7c into cncf:main Aug 25, 2025
1 check passed
@github-project-automation github-project-automation bot moved this from New to Done in CNCF TOC Board Aug 25, 2025
@pacoxu pacoxu deleted the workloads branch September 15, 2025 10:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

7 participants