Deployment

Deployment of Renovate

Follow the Extra Package Deployment Guide

Example Deployment Values

packages:
  renovate:
    enabled: true
    git:
      repo: https://repo1.dso.mil/big-bang/product/packages/renovate.git
      tag: 32.38.0-bb.1
    values:
      networkPolicies:
        enabled: "{{ $.Values.networkPolicies.enabled }}"
      istio:
        enabled: "{{ $.Values.istio.enabled }}"
      cronjob:
        schedule: '0 1 * * *'
      renovate:
        config: |
        {
            "platform": "gitlab",
            "endpoint": "https://gitlab.example.com/api/v4",
            "token": "your-gitlab-renovate-user-token",
            "autodiscover": "false",
            "dryRun": true,
            "printConfig": true,
            "repositories": ["username/repo", "orgname/repo"]
        }

Config

The configuration sets up a self-hosted instance of Renovate that connects with a platform. In the example, we connect to GitLab using the GitLab API v4 at a specified URL.

Auth

It is recommended to use a repository-scoped auth token with developer access for least privilege.

Repositories

The repositories key in this self-hosted renovate configuration specifies which repositories should be included in the update checks performed by renovate Accepts an array of strings or objects.

See Self Hosted Configuration for more details

Cron Job

Refer to the Scheduling Renovate Guide.

Individual Package Configuration

The configuration file for Renovate is called renovate.json and is located in each project’s root directory. See Package Configuration

---

Last update: 2024-07-16 by Michael Martin