Skip to content

Report Kubernetes object ownership on the k8s-status service message - #2150

Draft
eddymoulton wants to merge 1 commit into
mainfrom
worktree-kubernetes-tree-spike
Draft

Report Kubernetes object ownership on the k8s-status service message#2150
eddymoulton wants to merge 1 commit into
mainfrom
worktree-kubernetes-tree-spike

Conversation

@eddymoulton

Copy link
Copy Markdown
Contributor

Adds an optional ownerUuid property carrying the uid of the owner reference marked controller: true, so Server can render a deployment's objects as an ownership tree. The property is omitted entirely when an object has no controlling owner, which is the case for objects Octopus applies directly.

Older servers ignore the new property: the service message parser dumps every attribute into a plain dictionary and the k8s-status mapper reads known keys by name, so no capability gate is needed.

⚠️ Does this change require a corresponding Server Change?
⚠️ If so - please add a "Requires Server Change" label to this PR!

Adds an optional ownerUuid property carrying the uid of the owner reference marked controller: true, so Server can render a deployment's objects as an ownership tree. The property is omitted entirely when an object has no controlling owner, which is the case for objects Octopus applies directly.

Older servers ignore the new property: the service message parser dumps every attribute into a plain dictionary and the k8s-status mapper reads known keys by name, so no capability gate is needed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant