Clemens Beck (b383749c) at 18 Mar 15:31

Clemens Beck (3b6df443) at 18 Mar 15:27

What does this MR do?

Update NGINX Ingress to 1.15.0

• Update chart version by using scripts/update-nginx-chart.sh.
• Update default image tag to 1.15.0.

Changelog: changed

Related issues

Closes #6331

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

• MR has a green pipeline on https://gitlab.com/gitlab-org/charts/gitlab.
• Consider downstream impact to the Operator, as per evaluating impact from changes to GitLab chart.

Clemens Beck (6272cf73) at 18 Mar 14:41

... and 1 more commit

🔗 Fixes https://gitlab.com/gitlab-org/cloud-native/mirror/images/-/jobs/13546833619

Clemens Beck (47d18b28) at 18 Mar 14:16

Clemens Beck (57b0d498) at 18 Mar 14:08

Clemens Beck (585cb2c6) at 18 Mar 14:05

Update to 1.15.0 following the process documented in !34.

Relates gitlab-org/charts/gitlab#6331

Relates gitlab-org/charts/gitlab#6331

Clemens Beck (b3773a49) at 18 Mar 13:46

fyi @lucus.li

Clemens Beck (98ac3a48) at 18 Mar 12:05

Clemens Beck (aea89672) at 18 Mar 12:03

What does this MR do?

Restructure Gateway API and Envoy Gateway documentation

Closes #6328

Related issues

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

• MR has a green pipeline on https://gitlab.com/gitlab-org/charts/gitlab.
• Consider downstream impact to the Operator, as per evaluating impact from changes to GitLab chart.

Clemens Beck (0d36e1fc) at 18 Mar 11:59

... and 4 more commits

What does this MR do?

Exposes OpenBao database configuration at the GitLab chart level via global.openbao.psql and fixes database precedence so connection.database overrides global.openbao.psql.database when both are set.

Closes #590085

Changes

1. Template changes (templates/_openbao.tpl)

openbao.postgresql.configuration:

• Merges connection from global.psql → global.openbao.psql → connection
• Database precedence: connection.database > global.openbao.psql.database > "openbao"
• Ensures connection.database wins when both connection and global.openbao.psql are set

2. Removed openbao.psql

• Dropped the openbao.psql subchart-level config; use global.openbao.psql or connection instead
• templates/_removals.tpl: Blocks upgrade if openbao.psql is still configured

3. Defaults (values.yaml)

• global.openbao.psql.database: openbao so toolbox and other consumers get the default database name
• connection.database: '' so global.openbao.psql.database applies when not overridden

4. Config check (templates/_checkConfig_openbao.tpl)

• Unchanged: still requires database config when OpenBao is enabled with external PostgreSQL

5. Documentation (doc/charts/openbao/_index.md)

• Updated global.openbao.psql default and database precedence
• Clarified that connection.database overrides global.openbao.psql.database

6. Tests (spec/configuration/openbao_spec.rb)

• Precedence: connection.database overrides global.openbao.psql.database
• Custom database via global.openbao.psql.database

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

• MR has a green pipeline on https://gitlab.com/gitlab-org/charts/gitlab.
• Consider downstream impact to the Operator, as per evaluating impact from changes to GitLab chart.

Thanks for the review @ashvins. I responded to your question.

As I understand we are we are using Gateway API to replace Ingress right?

Correct, but one important differentiation: GitLab chart will continue to support Ingresses, but NGINX Ingress will be disabled (19.0) and dropped (20.0). This follow the official retirement of NGINX Ingress.

Gateway API is a modern replacement for Ingresses and Envoy Gateway is one available Gateway API provider/controller.

Where are we going to put the conditional routing spec? Like we did here?

The path-based conditional routing was a workaround specific to (NGINX) Ingress, necessary to prevent conflicts between the HTTP and gRPC Ingress. Since both traffic types are now consolidated under a single route, this path-level differentiation is no longer required.