tepichord/milner
1
1
Fork 0
Code Issues 8 Pull requests 5 Projects 1 Releases Packages Wiki Activity Actions

Create Tailscale egress from the cluster #92

Closed
tepichord wants to merge 0 commits from feat/87-tailscale-egress-from-cluster into main
pull from: feat/87-tailscale-egress-from-cluster
merge into: tepichord:main
Conversation 0 Commits - Files changed -
tepichord commented 2026-09-22 16:47:51 -07:00
Owner
Copy link

Closes #87

Automated PR created by forgejo-done adapter.

Closes #87 Automated PR created by forgejo-done adapter.
Refs: #87
Refs: #87
Refs: #87
Refs: #87
Refs: #87
Refs: #87
The §17 placement rationale claimed `annia`'s `baseline` label is what
admits the egress proxy pods. It is not: the operator runs ProxyGroup pods
in its own `tailscale` namespace (§3a), the one whose `privileged` label
covers them, so `annia`'s label governs annia's own workloads only.

Also record why the Service sits in the consumer's namespace — story 14's
"no real credential and no real power", so a preview path to an LLM is a
stub — and the fourth rule from the issue: one egress ProxyGroup serves
every egress Service.

Refs: #87
test(gitops): assert the egress Service's externalName, fix a stale rationale
All checks were successful
ci/woodpecker/pr/gates Pipeline was successful
Details
ci/woodpecker/pull_request_closed/cleanup Pipeline was successful
Details
b9d42aac7d 
The shape guard's docstring names the `externalName` rule it did not
check: an ExternalName Service the API server accepts needs a non-empty
one, and the literal is the human record of intent the operator later
overwrites. Assert it, so dropping the field fails offline rather than at
admission.

The namespace guard's docstring also attributed the `baseline` label to
the egress proxy pods; those run in the operator's `privileged` `tailscale`
namespace (§3a). Say what the label actually governs.

Refs: #87
tepichord 2026-09-24 18:11:22 -07:00
  • closed this pull request
  • removed the
    pr
    reviewing
         label
All checks were successful
ci/woodpecker/pr/gates Pipeline was successful
Required
Details
ci/woodpecker/pull_request_closed/cleanup Pipeline was successful
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
blocked

   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
effort
high

  
effort
low

  
effort
medium

  
effort
minimal

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
pr
feedback
Used for PRs, indicates that feedback has been given and agent needs to make changes

  
pr
reviewing
Used for PRs, indicates that a human is waiting to review the pull request, no action needed by the agent

  
question

More information is needed

  
status
backlog
Ignore, no work needed yet, human will assign this work by changing to status/planning

  
status
document
Record findings, create flashcards, and document knowledge in knowledgebase for the future

  
status
done
Completed when PR is merged, no more work needed.

  
status
implement
Make the code changes. Should be done by a faster and cheaper model

  
status
pending
Give human a chance to review planning details

  
status
planning
Ready to begin. Fill out implementation details and things like acceptance criteria, etc. A smarter thoughtful llm should be delegated for this

  
status
reviewing
PR is created and feedback loop begins between human and agent

  
waiting

   
wontfix

This won't be fixed

No labels
blocked
bug
duplicate
effort
high
effort
low
effort
medium
effort
minimal
enhancement
help wanted
invalid
pr
feedback
pr
reviewing
question
status
backlog
status
document
status
done
status
implement
status
pending
status
planning
status
reviewing
waiting
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
tepichord/milner!92
No description provided.