Display warning when agent is already blocked or allowed
Issue: FE: Display a warning message when a cluster ag... (#464272 - closed)
What does this MR do and why?
NOTICE This feature is behind the remote_development_namespace_agent_authorization
feature flag.
In the Agent Authorization UI, a user can block or allow a cluster agent for creating Workspaces. If the user attempts to change a cluster agent's status to blocked or allowed, but the status was already changed elsewhere, the UI displays a warning message indicating this.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
-
Enable the
remote_development_namespace_agent_authorization
feature flag:rails c && Feature.enable(:remote_development_namespace_agent_authorization)
-
Follow these instructions to register two cluster agents in the
gitlab-org
group:- Create a project in the group
gitlab-org
namedworkspaces-agents-config
. - Create two directories in the project's repository:
.gitlab/agents/remote-dev
.gitlab/agents/remote-dev-two
- Create a project in the group
-
In each directory, create a file named
config.yaml
with the following contentremote_development: enabled: true dns_zone: workspaces.localdev.me # below configuration is optional # they override the default values network_policy: enabled: true # if your GDK is configured on a public IP, you don't need to set the `egress` key in this section. egress: - allow: '0.0.0.0/0' except: - '10.0.0.0/8' - '172.16.0.0/12' - '192.168.0.0/16' # if your GDK is configured on a different private IP, use that in the line below. - allow: '172.16.123.1/32' # for debugging locally to increase log verbosity observability: logging: level: debug grpc_level: warn
-
To connect the cluster agents:
- In the
workspaces-agent-config
project, navigate to Operate -> Kubernetes Clusters. - Click the button "Connect to cluster" and select the "remote-dev" agent. Connect the cluster and close the modal dialog. It doesn't matter if the cluster is not connected.
- Repeat step 2 for the "remote-dev-two" agent.
- In the
-
Open the URL http://gdk.test:3000/groups/gitlab-org/-/settings/workspaces in two tabs.
-
In the first tab, allow one of the agents.
-
In the second tab, allow the same agent. You should see a warning message indicating that the agent has already been allowed.