Update Jetstream catalog to support MaxText and Pytorch

[rlakhtakia]

• Create new subdirectories for MaxText & Pytorch

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: rlakhtakia / name: Radhika Lakhtakia (27f2718, a907ca4, bf7e7f5)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rlakhtakia
Once this PR has been reviewed and has the lgtm label, please assign jjk-g for approval. For more information see the 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:

• serving-catalog/OWNERS

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

[k8s-ci-robot]

Welcome @rlakhtakia!

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

[jjk-g]

Thanks for improving this!

Let's remove the llama and gemma examples under the jetstream/ directory and just switch to their respective maxtext and pytorch subdirectories. Also remove the pytorch llama3-8b for now.

Then also comment validating the yamls deploy and the model servers start correctly.

[ArangoGutierrez]

#30 (comment)

[Copilot]

Pull Request Overview

Adds support for JetStream-PyTorch (gemma-7b-it) and JetStream-MaxText (llama3-8b) by creating dedicated gke overlays and base patches for both models.

• Introduces new gke overlay directories with job, deployment, HPA, and README for PyTorch and MaxText.
• Adds base kustomization and patch files for service, job, and deployment under each model.
• Removes unused kaggle mounts from the shared base job and cleans up legacy definitions.

Reviewed Changes

Copilot reviewed 30 out of 30 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
serving-catalog/core/deployment/jetstream/pytorch/gemma-7b-it/gke/job.patch.yaml	New TPU job overlay
serving-catalog/core/deployment/jetstream/pytorch/gemma-7b-it/gke/hpa.patch.yaml	HPA patch for inference server
serving-catalog/core/deployment/jetstream/pytorch/gemma-7b-it/gke/deployment.patch.yaml	Deployment labels for gemma-7b-it
serving-catalog/core/deployment/jetstream/pytorch/gemma-7b-it/gke/README.md	Usage instructions
serving-catalog/core/deployment/jetstream/pytorch/gemma-7b-it/base/*	Base patches and kustomization for gemma-7b-it
serving-catalog/core/deployment/jetstream/maxtext/llama3-8b/gke/*	New GKE overlay for llama3-8b
serving-catalog/core/deployment/jetstream/maxtext/llama3-8b/base/*	Base patches and kustomization for llama3-8b
serving-catalog/core/deployment/jetstream/base/job.yaml	Removed legacy kaggle mounts

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Reopen this PR with /reopen
• Mark this PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closed this PR.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Reopen this PR with /reopen
• Mark this PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/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-sigs/prow repository.