Skip to content

Add read-only YAML view for a Kubernetes resource detailed view

What does this MR do and why?

This MR adds a read-only YAML view for the spec and status fields for all the workload types. We don't know exactly which fields can be returned for each specific workload type and request all of them.

This functionality is already added for the pods page within !144237 (merged)

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.

Page Before After
CronJobs

Screenshot_2024-02-27_at_15.17.39

Screenshot_2024-02-27_at_15.10.45

DaemonSets

Screenshot 2024-02-27 at 15.18.35.png

Screenshot 2024-02-27 at 15.09.44.png

Deployments

Screenshot 2024-02-27 at 15.18.56.png

Screenshot 2024-02-27 at 15.09.31.png

Jobs

Screenshot 2024-02-27 at 15.19.12.png

Screenshot 2024-02-27 at 15.09.18.png

ReplicaSets

Screenshot 2024-02-27 at 15.19.44.png

Screenshot 2024-02-27 at 15.09.06.png

StatefulSets

Screenshot 2024-02-27 at 15.19.59.png

Screenshot 2024-02-27 at 15.08.32.png

Services

Screenshot 2024-02-27 at 15.20.15.png

Screenshot 2024-02-27 at 15.08.52.png

How to set up and validate locally

  1. Enable the k8s_dashboard feature flag
      Feature.enable(:k8s_dashboard)
  1. Enable KAS on your GDK (steps 1-2 from the guide).

  2. 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.
  3. 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>
  4. 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.

  5. Navigate to:

    • https://gdk.test:3443/-/kubernetes/<yout-agent-id>/cronJobs
    • https://gdk.test:3443/-/kubernetes/<yout-agent-id>/daemonSets
    • https://gdk.test:3443/-/kubernetes/<yout-agent-id>/deployments
    • https://gdk.test:3443/-/kubernetes/<yout-agent-id>/jobs
    • https://gdk.test:3443/-/kubernetes/<yout-agent-id>/replicaSets
    • https://gdk.test:3443/-/kubernetes/<yout-agent-id>/statefulSets
    • https://gdk.test:3443/-/kubernetes/<yout-agent-id>/services
  6. Verify the page, it's data and the drawer appearing on the table row click.

Related to #438022 (closed)

Edited by Anna Vovchenko

Merge request reports