Repository navigation
feat: add hyperpod-resource-ownership subchart, disabled by default - #483
Closed
meghanajs99 wants to merge 1 commit into
Closed
meghanajs99 wants to merge 1 commit into
meghanajs99 wants to merge 1 commit into
Conversation
Records who created each RayJob, HyperPodPyTorchJob, InferenceEndpointConfig and JumpStartModel, and lets only the creator, the operators and cluster admins update or delete the ones marked OwnerOnly. The webhook image is resolved per region from the HyperPod ECR accounts, by tag (default 1.0.20.0_1.0.3.0) or by digest.
meghanajs99
requested a deployment
to
manual-approval
November 21, 2026 20:30 — with
GitHub Actions
Waiting
Contributor
Author
|
Closing in favor of a single sync PR that merges the staging repository's master into main, once the staging PRs for these charts have merged. |
This branch is waiting to be deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What's changing and why?
Adds HyperPod resource ownership to the HyperPod Helm chart as the
hyperpod-resource-ownershipsubchart. It records who created each RayJob, HyperPodPyTorchJob, InferenceEndpointConfig and JumpStartModel, and lets only the creator, the operators and cluster admins update or delete the ones markedOwnerOnly.The subchart is disabled by default (
hyperpod-resource-ownership.enabled: false). Existing installs and upgrades are unchanged unless it is turned on.Changes:
HyperPodHelmChart/Chart.yaml: new dependencyhyperpod-resource-ownership(file://), withcondition: hyperpod-resource-ownership.enabled.HyperPodHelmChart/values.yaml:hyperpod-resource-ownershipblock,enabled: false.charts/hyperpod-resource-ownership/: the mutating webhook that records the creator, ValidatingAdmissionPolicies that enforceOwnerOnly(including status and scale writes), the webhook Deployment, Service, PodDisruptionBudget and ServiceAccount, and cert-manager Issuer and Certificate for its TLS.region, thenglobal.region), by tag (default1.0.20.0_1.0.3.0) or byimage.digest.image.overridesets the full URI.helm_chart/readme.md: new row in the components table.Before/After UX
Before:
The HyperPod Helm chart has no resource ownership.
After:
Default install: no change; the subchart renders no objects.
Opt in (requires cert-manager and Kubernetes 1.30+):
How was this change tested?
helm dependency update+helm lint HyperPodHelmChart: 0 failed, with the subchart off and on.helm template(default): 0 objects from the subchart.helm template --set hyperpod-resource-ownership.enabled=true --set global.region=<region>: renders the webhook, policies and certificates; the image is the right regional account and tag in each of the 14 Regions, andimage.digestrendersrepository@sha256:….hyperpod-resource-ownership-webhook:1.0.20.0_1.0.3.0exists in all 14 regional ECR repositories (one digest).Are unit tests added?
No; this adds a Helm subchart. The webhook and policies are tested in their own packages.
Are integration tests added?
No in this repository; the resource ownership integration tests run against live clusters in its pipeline.