-
Notifications
You must be signed in to change notification settings - Fork 17
Open
Milestone
Description
Managing support sessions for worker nodes in clusters with many nodes and applications is cumbersome when only the app public FQDN is known. It is difficult to determine the node ID needed to start a support session.
Proposed solution
Develop a helper command that:
- Accepts one or more of: app FQDN, module ID, module ui_name, node ui_name
- Resolves the correct node ID
- Starts the support session on the node
- Returns match details and the Support ID to the operator
For example, given app FQDN:
# supportctl start nethvoice.example.org
Application: myPBX (nethvoice4)
Node: w4@ams3
- ID: 2
- VPN IP: 10.5.4.2
- FQDN: node4.example.org
- Default IP: 88.72.63.54
Support ID: 89673a89-bf82-44f8-803b-3b38a793721e
Alternative solutions
Manual lookup of node IDs via existing dashboard or API options; not user-friendly in large clusters.
Additional context
Current workflow is not scalable for clusters with many nodes and apps.
See also
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
ToDo