重要
Agent Control and New Relic Control are now generally available for Kubernetes! Support for Linux hosts and Windows hosts is also in public preview program, pursuant to our pre-release policies.
By default, Agent Control uses docker.io as the Open Container Initiative (OCI) registry to download agent packages and agent type definitions. If your environment requires a different registry, for example an air-gapped environment, you can configure a custom OCI registry or mirror.
Mirror signed artifacts
Every agent package and agent type definition is signed with a detached sigstore/cosign signature artifact. Your mirror must also serve this signature artifact alongside the package itself to keep Agent Control signature verification working.
Before you begin
Before configuring a custom OCI registry, ensure you have:
- Installed Agent Control: Use the New Relic CLI to complete the Agent Control installation.
- Mirror registry available: Ensure your custom OCI registry is accessible from the host machine.
- CA certificate installed: Install the certificate authority certificate on the host machine required to communicate with the mirror.
Configure on hosts
After installing Agent Control on your host, follow these steps to configure a custom OCI registry:
Edit the local configuration file
Edit the Agent Control local configuration file:
- Linux:
/etc/newrelic-agent-control/local-data/agent-control/local_config.yaml - Windows:
C:\Program Files\New Relic\newrelic-agent-control\local-data\agent-control\local_config.yaml
Add the following configuration sections to the file:
oci: registry: YOUR_REGISTRY_URLIf you need to set up your username and password, use the following snippet:
oci: registry: YOUR_REGISTRY_URL auth: basic: username: YOUR_USERNAME password: YOUR_PASSWORDReplace the placeholder values:
YOUR_REGISTRY_URL: The URL of your custom OCI registry (for example,registry.example.com:5000ormirror.internal.company.com)YOUR_USERNAME: Username for registry authenticationYOUR_PASSWORD: Password for registry authentication
This setting applies to both agent packages and agent type definitions, since both are pulled through the same oci.registry.
Restart Agent Control
Restart the Agent Control service to apply the new configuration and verify that the service restarted successfully
Linux:
bash$sudo systemctl restart newrelic-agent-control$sudo systemctl status newrelic-agent-controlWindows:
Restart-Service -Name newrelic-agent-controlGet-Service -Name newrelic-agent-control