-
Notifications
You must be signed in to change notification settings - Fork 0
[Agent] Implement registration and outbound mTLS enrollment #2
Copy link
Copy link
Open
Labels
area/agentOutbound cluster connector and Helm packagingOutbound cluster connector and Helm packagingarea/securitySecurity, identity, RBAC, and complianceSecurity, identity, RBAC, and compliancekind/featureNew product capabilityNew product capabilitypriority/criticalRequired on the current critical pathRequired on the current critical pathsize/mMedium, normally one to two daysMedium, normally one to two dayssprint/currentCurrent execution setCurrent execution set
Description
Activity
Metadata
Metadata
Assignees
Labels
area/agentOutbound cluster connector and Helm packagingOutbound cluster connector and Helm packagingarea/securitySecurity, identity, RBAC, and complianceSecurity, identity, RBAC, and compliancekind/featureNew product capabilityNew product capabilitypriority/criticalRequired on the current critical pathRequired on the current critical pathsize/mMedium, normally one to two daysMedium, normally one to two dayssprint/currentCurrent execution setCurrent execution set
Type
Projects
- StatusShow more project fieldsBacklog
Context
The connector must enroll without an uploaded kubeconfig or long-lived shared secret. The control plane contract is defined in KubeOrch/core#122; this issue implements only the cluster-side one-time registration and outbound mTLS identity lifecycle.
Outcome
A fresh agent can exchange a one-time registration credential for a workspace-bound mTLS identity, establish an authenticated outbound connection, and recover safely across restart without replaying enrollment.
Scope
Out Of Scope
Acceptance Criteria
Verification
Dependencies
Blocked by KubeOrch/core#122 and the agent scaffold issue.
Documentation And Observability
Document certificate storage, rotation, recovery, and operator-visible connection states. Emit connection metrics using only non-sensitive IDs.