Skip to content

[Feature flag] Enable k8s Watch API

Anna Vovchenko requested to merge 427762-feature-flag-enable-k8s-watch-api into master

What does this MR do and why?

This MR enables the k8s_watch_api feature flag and cleanups the code.

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.

No visual changes as the feature flag was already enabled by default since %16.7.

How to set up and validate locally

Prerequisites:

  1. Visit the Project -> Operate -> Environments

  2. Create/Edit an environment using the UI

  3. Visit the Project -> Infrastructure -> Kubernetes clusters page and create an agent following the instructions from the modal.

    • Select the "Connect a cluster" button
    • The modal should pop up
    • In the modal select "Select an agent or enter a name to create new"
    • You probably won't have any configured agents to show up in the list, create a new one by typing the name of your choice
    • The button should appear at the bottom of the list saying "Create agent: <your-agent-name>"
    • Select the button and click "Register" in the next view.
    • Save the token to use it in the next point.
  4. Add the following configuration inside your project in .gitlab/agents/<your-agent-name>/config.yaml for the user_access agent:

    user_access:
      access_as: 
        agent: {}
      projects:
      - id: <your-group>/<your-project-to-share-agent-with>
  5. Note that the shared agents should be connected to the cluster in order to appear in the list. Please follow points 3-8 from the guide and then the Deploy the GitLab Agent (agentk) with k3d section to create a local cluster and connect your agent with the cluster.

  6. Select an agent from the dropdown in the Environments settings page and save the change.

  7. Visit the Environments page and visit the environment details page for the environment that has an associated agent.

  8. Update resources in your cluster to verify the watch API works and updates the UI accordingly.

Review progress:

Related to #427762 (closed)

Edited by Anna Vovchenko

Merge request reports