Skip to main content
Connect GitLab so RubixKube agents can see what shipped through your pipelines, correlate CI deployments with incidents, and propose soft remediations as merge requests instead of direct cluster changes.

​
What it unlocks

Pipelines and MRs in context

Agents can read recent deploys, merges, and commit history. RCAs cite pipeline runs that correlate with an incident when the evidence points that way.

Merge requests as a remediation surface

For IaC and GitOps repos, agents can open MRs with the proposed change. Your review, your merge, your pipeline.

Issue tracking

Agents can create, read, and update issues linked to insights and RCA reports.

Evidence, not source

The integration reads metadata and diffs. Source code is not ingested or stored.

​
Connect it

1

Open the Integrations page

In the RubixKube console, go to Integrations and select GitLab.
2

Authenticate

Authorise with GitLab. Both GitLab.com and self-hosted instances are supported. For self-hosted, provide your GitLab base URL.
3

Configure access

Pick the groups or projects RubixKube can see. Grant write access only to projects where you want agents to open merge requests.
Once connected, GitLab is available tenant-wide. Every agent across every environment can use it without additional per-environment setup.

​
How the agents use it

  • During RCA, agents walk recent pipelines and merges to the affected service as candidate causes, citing them as evidence.
  • For IaC and GitOps-managed infrastructure, soft remediations are proposed as merge requests against the relevant project. See Safety and Guardrails for the full approval model.
  • Chat can answer questions like “what changed in payments before this spike” by walking the pipeline and merge history.

​
Build custom workflows with skills

Out of the box, the integration exposes read and MR-open capabilities to agents. To program specific workflows (auto-open an MR with a suggested config fix, weekly changelog digest, project-to-service mapping rules), build a Skill on top of the connection.

​
Self-hosted GitLab

Self-hosted instances work the same way. Provide your instance’s base URL during setup. For restricted networks, reach out to connect@rubixkube.ai and we will walk you through the right deployment mode.

​
Troubleshooting

Confirm the authorised account has access to the group or project, and that the project is included in the scope you chose during setup.
Check that the target project is included in the write scope. Reads work with a narrower scope than writes.

GitHub

Equivalent integration for GitHub-hosted repos.

Skills

How to compose GitLab tools into custom workflows.

Safety and Guardrails

Why MR-based remediation is the preferred path.