Networks
此内容尚不支持你的语言。
The container networks a deployment attaches to, and what is attached to each.
Every address below is served under the control plane’s base URL. Permission is the guard the route is registered with; who holds it is read from the control plane’s own grant, so it cannot drift from what the server does. A dash means the route carries no permission guard of its own — the access tier below the table is then the whole of what stands in front of it.
Generated from Route. Hand edits to this table are overwritten on the next build — change the Go doc comment, or the generator.
| Route | Permission | Who holds it | Body |
|---|---|---|---|
GET /api/v1/networks |
networks:read |
developer, operator, readonly, support |
— |
POST /api/v1/networks |
networks:manage |
operator |
— |
DELETE /api/v1/networks/{name} |
networks:manage |
operator |
— |
GET /api/v1/networks/{name} |
networks:read |
developer, operator, readonly, support |
— |
PUT /api/v1/networks/{name} |
networks:manage |
operator |
— |
POST /api/v1/networks/{name}/connect |
networks:manage |
operator |
— |
POST /api/v1/networks/{name}/disconnect |
networks:manage |
operator |
— |
Who can reach these at all
Section titled “Who can reach these at all”authenticated — Behind authentication, cross-site-request-forgery validation and tenant extraction. Every call acts inside exactly one tenant.