Skip to content

Remove starboard directive from config

What does this MR do and why?

Currently, OCS can be configured using 2 directives starboard and container_scanning. This MR removes the starboard directive as it is scheduled for removal in %16.0

MR I referenced that added the container_scanning directive: Add container_scanning for starboard configurat... (!729 - merged)

Note that only Agent Configuration is affected. Scan execution policies does not rely on the starboard directive.

How to set up and validate locally

  • Same setup steps as this MR
  • Run a scan using the container_scanning directive in the Agent Configuration. The scan should succeed.
    container_scanning:
      cadence: '0 0 * * *'
      vulnerability_report:
        namespaces:
          - default
          - kube-system
  • Run a scan using the starboard directive. There should be an error with msg GetConfiguration.Recv failed... unknown field \"starboard\"
    starboard:
      cadence: '0 0 * * *'
      vulnerability_report:
        namespaces:
          - default
          - kube-system

Related to: Remove support for `starboard` directive (gitlab-org/gitlab#387559 - closed)

Merge request reports