you tried

Relates to #220

Changes

This MR adds a new diagnostic check to detect gpg_key_subkeys records with NULL user_id values that will cause GitLab 18.9 upgrade failures.

Check File Details:

• Location: checks/database_primary_node/20260225_220.yml
• Title: "18.9 upgrade failure due to NULL user_id in gpg_key_subkeys"
• Reference: gitlab-org/gitlab#590901
• Version Started: 18.8.0
• Version Fixed: (not yet fixed)
• Workaround: gitlab-org/gitlab#590901 (comment 3100188170)

Command Behavior: The check runs a PostgreSQL query to count gpg_key_subkeys records with NULL user_id:

SELECT COUNT(id) FROM gpg_key_subkeys WHERE user_id IS NULL;

Using inverted exit code pattern:

• Exit 0 (issue FOUND): When non-zero count detected (NULL user_id records exist)
• Exit 1 (healthy): When count is zero (no NULL user_id records)

The check warns administrators before attempting 18.9 upgrade, allowing them to apply the workaround to clean up orphaned records.

Relates to #220

Changes

This MR adds a new diagnostic check to detect gpg_key_subkeys records with NULL user_id values that will cause GitLab 18.9 upgrade failures.

Check File Details:

• Location: checks/database_primary_node/20260225_220.yml
• Title: "18.9 upgrade failure due to NULL user_id in gpg_key_subkeys"
• Reference: gitlab-org/gitlab#590901
• Version Started: 18.8.0
• Version Fixed: (not yet fixed)
• Workaround: gitlab-org/gitlab#590901 (comment 3100188170)

Command Behavior: The check runs a PostgreSQL query to count gpg_key_subkeys records with NULL user_id:

SELECT COUNT(id) FROM gpg_key_subkeys WHERE user_id IS NULL;

Using inverted exit code pattern:

• Exit 0 (issue FOUND): When non-zero count detected (NULL user_id records exist)
• Exit 1 (healthy): When count is zero (no NULL user_id records)

The check warns administrators before attempting 18.9 upgrade, allowing them to apply the workaround to clean up orphaned records.

Jessie Lee (5848d269) at 11 Mar 20:08

  gitlab-rails runner "broken = 0; MergeRequestDiff.where(stored_externally: true).limit(100).each { |d| d.diffs.first(1) rescue broken += 1 }; exit 0 if broken > 10"

new line at end of file

Jessie Lee (26b0a60c) at 11 Mar 20:04

Jessie Lee (a3fa5f04) at 11 Mar 20:04

WARNING: Duo did some of this please check carefully

This merge request adds support for checking GitLab installations that use Helm

The main changes include:

1. New check for deprecated components: Added a warning system that detects when GitLab Helm installations are using bundled PostgreSQL or Redis components that will be removed in version 19.0, helping users prepare for upgrades.

2. Kubernetes integration: Enhanced the tool to work with Kubernetes clusters by adding support for kubeconfig files (Kubernetes configuration files) and the ability to run checks against containerized GitLab deployments.

3. Authentication handling: Added smart credential resolution that can work with various Kubernetes authentication methods (like cloud provider plugins) by converting them to simple tokens that work inside containers.

4. Inventory system updates: Extended the host inventory system to include "helm_nodes" as a new type of deployment target, allowing users to specify Kubernetes namespaces instead of traditional server addresses.

5. Version detection improvements: Added the ability to detect GitLab versions from Helm chart deployments by examining container images

Jessie Lee (3f8c638c) at 11 Mar 16:26

... and 13 more commits