Rename to compute and tidy up the install bundle#83
Merged
Conversation
- Resources now use stable, predictable names (compute, compute-webhook, compute-config, etc.) so consumers can reference them directly without kustomize name prefixes. - Add a single-cluster install path under config/single-cluster for the common case of installing everything on one cluster. - Reorganize RBAC into reusable components (controller_rbac for the controller's permissions, leader_election for leader election only) so the install bundle composes cleanly. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The webhook server config is now optional. When omitted, the manager starts without an admission webhook server, so consumers that don't need admission webhooks no longer have to provision a serving certificate just to keep the manager from crashing on startup. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
scotwells
force-pushed
the
refactor/rename-to-compute
branch
2 times, most recently
from
82c08e6 to
29aaaa2
Compare
This repo owns the entire compute.datumapis.com API group, but its name, import paths, and image names still said "workload-operator" from when it only managed the Workload resource. Renaming to "compute" lines the project up with what it actually owns. What this changes: - Go import path: go.datum.net/workload-operator -> go.datum.net/compute - Container image: ghcr.io/datum-cloud/workload-operator -> ghcr.io/datum-cloud/compute - Install bundle: ghcr.io/datum-cloud/workload-operator-kustomize -> ghcr.io/datum-cloud/compute-kustomize What does NOT change: - The compute.datumapis.com API group (Workload, WorkloadDeployment, Instance) - existing resources keep working with no migration. - Leader election lease key, so there are no orphaned leases on cutover. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
scotwells
force-pushed
the
refactor/rename-to-compute
branch
from
29aaaa2 to
60826a7
Compare
kevwilliams
approved these changes
Apr 9, 2026
This was referenced Apr 9, 2026
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
2 participants
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 this changes
This repo is being renamed from workload-operator to compute to match the API group it actually owns (
compute.datumapis.com). At the same time, the install bundle gets a long-overdue cleanup so consumers can pull it in without juggling kustomize prefixes.Three things in one PR
compute,compute-webhook, andcompute-config. A newsingle-clusterinstall path bundles everything you need for the common case of installing on a single cluster.workload-operatortocompute.What does NOT change
compute.datumapis.comAPI group is unchanged. ExistingWorkload,WorkloadDeployment, andInstanceresources keep working with no migration.For consumers
This is a coordinated breaking change. Anything that imports
go.datum.net/workload-operator, pullsghcr.io/datum-cloud/workload-operator, or references the old kustomize bundle needs to switch to thecomputeequivalents at the same time this lands.Reading order for reviewers
The PR is split into three commits so it's easier to follow: