Skip to main content
Skip table of contents

Renovate Enterprise

Introduction

Renovate Enterprise is Mend’s paid, Renovate-only feature that allows users to implement Renovate on their SCM environment and allows them to scale up Renovate processes as needed. As this is a paid version of Renovate, all functionality is available, including Smart Merge Control.

Infrastructure and Setup

Renovate Enterprise works with scaling systems such as Kubernetes. As such, there is some need-to-know infrastructure information around this. A simple diagram showing the overall setup is shown below:

Renovate Enterprise Infrastructure.png

Ingress Point

The ingress point can be any form of entry into the network where the Renovate containers live. Whether this is on AWS EKS, Azure Kubernetes Service, or another form. The Renovate Server exposes port 8080 as a default, and therefore the Ingress point must allow this port to be accessible by the SCM system, whether hosted on a private network, or cloud-hosted.

Renovate Worker/Server Relationship

Renovate workers may be scaled up as needed without worry from a functionality perspective. But there may only be 1 Renovate Server in an environment at any given moment. This is due to the fact that the Server hosts a queue for all Worker jobs to pull from, and if two Renovate Servers are present, then the queue on each server will very quickly become out of sync and cause major issues.

Other Networking Related Considerations

When creating your environment, there are other networking considerations to take into place. This includes:

  • Log Output - There are some open source logging solutions available, such as Graylog. Splunk/Datadog work as well.

  • Renovate Worker → SCM System Connectivity - The Renovate Workers themselves require access to repositories that need to be scanned by Renovate. Make sure that nothing blocks this outbound connection.

Private Registries

Renovate supports the ability to pull changelogs and upgrade information from private registries for dependency upgrade purposes. When implementing private registry support in your Renovate configuration, hostRules will typically allow customers to provide encrypted credentials in the repository, that let Renovate access those private registries. These credentials can be encrypted using: https://github.com/mend-toolkit/mend-examples/tree/main/Repo-Integration/Encryption.

NOTE: you must create your own GPG key without a passphrase for this to work properly. Please refer to our documentation on how to create a GPG key.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.