Allow to expose OpenBao via Gateway API

What does this MR do?

Allow to expose OpenBao via Gateway API

  • Bump OpenBao chart from 0.11.0 to 0.12.0 which features support for a HTTPRoute.
  • If Gateway API and the OpenBao chart are enabled, add a listener to the managed Gateway resource.

Closes gitlab-org/cloud-native/charts/openbao#32 (closed)

Test Plan

  1. Install GitLab with Envoy Gateway enabled (see the example values).

  2. Wait for the installation to complete.

  3. Confirm the Gateway resource has no openbao-web listener.

  4. Enable OpenBao (--set openbao.install=true and --set global.openbao.enabled=true).

  5. Confirm the Gateway resource has a openbao-web listener.

  6. Check OpenBao is accessible via it's external URL

    curl --silent https://openbao.<GITLAB DOMAIN>/v1/sys/health | jq
    {
      "initialized": true,
      "sealed": false,
      "standby": false,
      "performance_standby": false,
      "replication_performance_mode": "disabled",
      "replication_dr_mode": "disabled",
      "server_time_utc": 1767876410,
      "version": "2.4.1+v2.4.1-gitlab2",
      "cluster_name": "vault-cluster-e66f66b9",
      "cluster_id": "ecf8ab9c-e896-03e7-21c8-53afb46cf7f0"
    }

Author checklist

For general guidance, please follow our Contributing guide.

Required

For anything in this list which will not be completed, please provide a reason in the MR discussion.

  • Merge Request Title and Description are up to date, accurate, and descriptive.
  • MR targeting the appropriate branch.
  • MR has a green pipeline.
  • Documentation created/updated.
  • Tests added/updated, and test plan for scenarios not covered by automated tests.
  • Equivalent MR/issue for omnibus-gitlab opened.

Reviewers checklist

Edited by Clemens Beck

Merge request reports

Loading