Skip to content

Remove `flux_resource_for_environment` feature flag

What does this MR do and why?

This MR cleans up the flux_resource_for_environment feature flag.

Screenshots or screen recordings

No visual changes.

How to set up and validate locally

  1. Ensure your GDK is running on HTTPS

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

  3. Visit the Project -> Infrastructure -> Kubernetes clusters page and create an agent following the instruction 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. Please follow points 3-8 from the guide and then the (Optional) Deploy the GitLab Agent (agentk) with k3d section to create a local cluster and connect your agent with the cluster.

  5. Add the following configuration for your agent, commit the following on the default branch: .gitlab/agents/<your-agent-name>/config.yaml:

    gitops:
      manifest_projects:
      - id: <your-group>/<your-project>
    user_access:
      access_as: 
        agent: {}
      projects:
      - id: <your-group>/<your-project>
  6. Follow this guide to start with the Flux

  7. Visit the Environments page:

    • Project -> Operate -> Environments if the new navigation is enabled
    • Project -> Deployments -> Environments if the new navigation is not enabled
  8. Create/Edit an environment using the UI, select the agent created in the previous steps and the namespace used for the Flux setup

  9. Once the namespace is selected, verify the Flux resource selector is shown

  10. Navigate to the Environments page, toggle the environment, wait for the Kubernetes overview to appear, and verify the Flux sync label. Take a look into the network tab of the devtools inspector and make sure the proper Flux resource is fetched.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Review progress:

Related to #421416 (closed)

Edited by Miguel Rincon

Merge request reports