Install a Remote Network Agent in Your Cluster

Before you begin

You are familiar with what a a Remote Network Agent is and its core features.

Remote Network Agent installation methods

By default, you install a Remote Network Agent (RNA) with full access to your cluster by using one of the following:

• UI wizard
  • Use a UI wizard to generate an install script that includes Client Credentials.
  • Install using default configuration.
  • Not recommended for production environments.
• CLI
  • Install using default configuration.
  • Not recommended for production environments.
• kubectl
  • Install using default configuration.
  • Not recommended for production environments.
• Helm
  • Install using default or advanced configuration.
  • Advanced configuration](/remote-network-agent/install-helm/) recommended for production environments.

Before you begin

• You have a role that allows you to create Client Credentials and connect a Remote Network Agent.

  • For the UI and CLI methods, you do not need to create Client Credentials. Those methods create Client Credentials for you.

  • For the kubectl and Helm methods, you do need to create Client Credentials.

    Show how to create Client Credentials

    1. Access the CD-as-a-Service Console.
    2. Go to the Configuration tab.
    3. If you have more than one tenant, make sure you select the desired tenant in the User context menu.
    4. In the left navigation menu, select Access Management > Client Credentials.
    5. In the upper right corner, select New Credential.
    6. Create a credential for your RNA. Use a descriptive name for the credential that matches what it is being used for. For example, name the credentials the same as the account name you assigned the target deployment cluster if creating a credential for an Remote Network Agent (RNA).
    7. Select an RBAC role from the Select Roles list. You must assign an RBAC role in order for the credential to access CD-as-a-Service.
       • If the credential for is a Remote Network Agent, select Remote Network Agent.
       • If you plan to use the credential to deploy from a GitHub Action or similar tool, select Deployments Full Access.
    8. Note the values for both Client ID and Client Secret. You need these values when configuring the RNA or any other service that you want to grant access to. Make sure to store the secret somewhere safe. You are not shown the value again.
    
    

• You have access to your own Kubernetes cluster.

Install with default configuration

Default configuration:

• Namespace: armory-rna
• Permissions: Full access to your cluster
  

• Method:
• UI Wizard
• CLI
• kubectl
• Helm

kubectl create ns armory-rna; 
kubectl --namespace armory-rna create secret generic rna-client-credentials \
--type=string \
--from-literal=client-secret="<client-secret>" \
--from-literal=client-id="<client-id>";
kubectl apply -f "https://api.cloud.armory.io/kubernetes/agent/manifest?agentIdentifier=sample-cluster&namespace=armory-rna"

You can go to the Agents page in the CD-as-a-Service Console to verify that your RNA has been installed and is communicating with CD-as-a-Service. If you do not see the RNA, check your cluster logs to see if the RNA is running.

What’s next

• View your connected Remote Network Agents to see data such as the last time CD-as-a-Service detected a heartbeat.
• Install with advanced configuration options.