Skip to content

feat: Name the instance behind a network interface claim - #375

Draft
scotwells wants to merge 1 commit into
mainfrom
feat/network-interface-claim-attached-to
Draft

scotwells wants to merge 1 commit into
mainfrom
feat/network-interface-claim-attached-to

Conversation

@scotwells

Copy link
Copy Markdown
Contributor

Summary

An edge access log cannot report the instance a request was proxied to, because nothing tells the networking layer which instance a claimed interface belongs to.

This names the owning instance on each network interface claim compute creates, as an opaque reference the networking operator carries through to the edge Envoy cluster metadata the access log reads.

This depends on the reference field added upstream, so it does not build until that release lands and the module bump follows, and its checks stay red until then.

Depends on datum-cloud/network-services-operator#509.

Test plan

  • A created claim names its owning instance
  • The build goes green once the upstream release is bumped in

🤖 Generated with Claude Code

An edge access log cannot report the instance a request was proxied to,
because nothing tells the networking layer which instance a claimed
interface belongs to.

This sets the claim's attachedTo reference to the owning instance when
compute creates the claim. The networking operator carries it,
uninterpreted, onto the interface, the endpoint slice, and the edge
Envoy cluster metadata the access log reads.

This depends on the attachedTo field added upstream, so it does not
compile until that release lands and the module is bumped.

Key changes:
- set claim spec attachedTo to the owning instance on claim creation

Co-Authored-By: Claude Opus 4.8 <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