Solve how to store and configure root domains for GA4K
Requirement
In Remote Development, each agent will be controlling exposing multiple workspaces. Each workspace will be exposed on a given domain. All workspaces for an agent would have a common suffix.
e.g. Let's say there is an agent a1
, all workspaces managed by this agent would have the suffix a1.gitlab.workspaces
.
For workspace w1
under agent a1
, the domain would be w1.a1.gitlab.workspaces
For workspace w2
under agent a1
, the domain would be w2.a1.gitlab.workspaces
The agentk does not care about this domain suffix. Rails needs to know about this domain suffix for the given agent.
Questions
Need to ask Configure team
- Do all (agentk) modules of GA4K react to agent configuration changes and/or restart running processes if the configuration changes? Is there a precedent to just ignore the change for agent configuration changes in agentk?
- Is there an easy in Rails if an agent configuration has changed and retrieved values from it?
- Is there an existing example of agentk configuration where an configuration value is not really related to cluster configuration which is under the agent's control
Questions for Product/UX
Regardless of where the agent domain suffix is stored, how are we expecting the behaviour to be
- Restart/reconfigure all existing/new workspaces to reflect the new domain suffix
- Start/configure all new workspaces to reflect the new domain suffix while existing workspaces will have the old domain suffix
- Changing of agent domain suffix would be immutable. If the administrator wants to move workspaces over a new domain, they can create a new agent with new domain suffix.
Why
How
Meta
Reach out to the ~"group::configure" to talk through the concept of storing agent meta.