Skip to content

Update API endpoint for Flux resource

What does this MR do and why?

This MR updates the API endpoint for the Flux Kustomize resource to use the v1 version instead of the deprecated v1beta1.

  • On the environments settings page, we use the updated endpoint to select a Flux resource,
  • On the environments details page we update the API endpoint on the fly as the old endpoint is already stored in the database.

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

No visual changes.

How to set up and validate locally

  1. Follow this guide to start with the Flux.

  2. Visit the Environments page at Project -> Operate -> Environments page

  3. Create/Edit an environment using the UI

  4. Enable KAS on your GDK (steps 1-2 from the guide).

  5. 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.
  6. 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>
  7. 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.

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

  9. The Flux resource selector will appear. Verify the new endpoint with v1 instead of v1beta1 is used.

  10. Visit the Environments page and select the environment with an associated agent and Flux resource.

  11. Validate the Flux resource is requested at the new endpoint.

Related to #454806 (closed)

Merge request reports