ScaleOps Deployment via ArgoCD

Public Repository

Public Repository

Connect to the ScaleOps public Helm repository directly through ArgoCD.

• Administrative access to ArgoCD UI or CLI
• Your ScaleOps installation token

apiVersion: v1
kind: Secret
metadata:
  name: scaleops-helm-repo
  namespace: argocd
  labels:
    argocd.argoproj.io/secret-type: repository
stringData:
  url: "https://registry.scaleops.com/charts/"
  name: scaleops
  type: helm
  password: <YOUR_SCALEOPS_TOKEN>
  username: scaleops

kubectl apply -f scaleops-helm-repo-secret.yaml

Private Repository

Private Repository

If you need to use a private repository, follow these steps to pull the ScaleOps chart into your environment.

• Helm installed in your environment
• ScaleOps installation token
• Access to your private repository

Step 1: Add ScaleOps Repository

helm repo add scaleops --username scaleops --password <YOUR_SCALEOPS_TOKEN> \
  https://registry.scaleops.com/charts/

Step 2: Update Helm Repositories

helm repo update

Step 3: Pull ScaleOps Chart

helm pull scaleops/scaleops --untar

Step 4: Verify Chart Confirm the ScaleOps chart files are extracted in your current directory.

Step 5: Update Private Repository Use your organization’s process to add the ScaleOps chart to your private repository.

ArgoCD UI

ArgoCD UI

Deploy ScaleOps through the ArgoCD web interface.

• Administrative access to ArgoCD UI
• Repository configured (from previous section)
• Kubernetes cluster accessible to ArgoCD

Step 1: Access Applications Dashboard

1. Log in to ArgoCD UI
2. Click Applications in the navigation menu

Step 2: Create New Application Click + New App to start the deployment process.

Step 3: Configure General Settings

Step 4: Configure Source

Step 5: Configure Destination

Step 6: Helm Values Select Helm to enter the values for the required keys.

scaleopsToken: <YOUR_SCALEOPS_TOKEN>
clusterName: <CUSTOMER_NAME>-<YOUR CLUSTER'S NAME>
global:
  image:
    registry: registry.scaleops.com

Step 7: Create Click Create to deploy ScaleOps.

Step 8: Verify Deployment Once the sync process is complete, verify that the ScaleOps application is running correctly in your Kubernetes cluster. You can do this by checking the application status in the ArgoCD dashboard or by using kubectl commands to inspect the resources directly in your cluster.

ArgoCD CLI

ArgoCD CLI

Deploy ScaleOps using the ArgoCD command-line interface.

• ArgoCD CLI installed and configured
• ScaleOps installation token
• Cluster name for ScaleOps

Step 1: Login to ArgoCD

argocd login <SERVER> --username <USERNAME> --password <PASSWORD>

Step 2: Create Application Manifest Create scaleops-application.yaml:

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: scaleops
  namespace: argocd
spec:
  destination:
    namespace: scaleops-system
    server: "https://kubernetes.default.svc"
  source:
    repoURL: "https://registry.scaleops.com/charts/"
    targetRevision: 1.*
    chart: scaleops
    helm:
      parameters:
        - name: scaleopsToken
          value: <YOUR_SCALEOPS_TOKEN>
        - name: clusterName
          value: <CUSTOMER_NAME>-<YOUR CLUSTER'S NAME>
        - name: global.image.registry
          value: registry.scaleops.com
      releaseName: scaleops
  project: default
  syncPolicy:
    syncOptions:
      - CreateNamespace=true
    automated:
      selfHeal: true
      prune: true

Step 3: Deploy Application

argocd app create scaleops --file scaleops-application.yaml

Step 4: Verify Deployment

argocd app get scaleops

Kubectl

Kubectl

Deploy ScaleOps using kubectl for direct Kubernetes management.

• kubectl configured for your cluster
• ScaleOps installation token
• Cluster name for ScaleOps

Step 1: Create Application Manifest Create scaleops-application.yaml:

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: scaleops
  namespace: argocd
spec:
  destination:
    namespace: scaleops-system
    server: https://kubernetes.default.svc
  source:
    repoURL: https://registry.scaleops.com/charts/
    targetRevision: 1.*
    chart: scaleops
    helm:
      values: |-
        clusterName: <CUSTOMER_NAME>-<YOUR CLUSTER'S NAME>
        scaleopsToken: <YOUR_SCALEOPS_TOKEN>
        global:
          image:
            registry: registry.scaleops.com
  project: default
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
    syncOptions:
      - CreateNamespace=true

Step 2: Deploy Application

kubectl apply -f scaleops-application.yaml

Step 3: Verify Deployment

kubectl get app scaleops -n argocd -o yaml

Same Cluster - Automatic

Same Cluster - Automatic (Recommended)

When ArgoCD and ScaleOps run on the same cluster, integration happens automatically.

• ScaleOps automatically detects ArgoCD when you automate your first workload
• The scaleops-recommender service patches the argocd-cm ConfigMap
• ScaleOps managers are excluded from ArgoCD’s resource tracking

Ensure ScaleOps has permission to modify ConfigMaps in the ArgoCD namespace:

• scaleops-recommender needs ConfigMap write access to argocd namespace

The argocd-cm ConfigMap is updated to exclude these ScaleOps components:

• scaleops-hpa-controller
• scaleops-updater
• scaleops-recommender

Same Cluster - Manual

Same Cluster - Manual

Force manual integration by creating a trigger ConfigMap.

Create the trigger ConfigMap:

kubectl create cm -n scaleops-system scaleops-argo-manage

This forces ScaleOps to immediately modify the argocd-cm ConfigMap without waiting for the first workload automation.

Different Clusters

Different Clusters

When ArgoCD and ScaleOps run on separate clusters, manual configuration is required.

• Access to both ArgoCD and ScaleOps clusters
• Administrative permissions on ArgoCD cluster

Step 1: Edit ArgoCD ConfigMap

kubectl edit configmap argocd-cm -n argocd

Step 2: Add ScaleOps Exclusions
Add the following to the ConfigMap:

apiVersion: v1
data:
  resource.customizations.ignoreDifferences.all: |
    managedFieldsManagers:
    - scaleops-hpa-controller
    - scaleops-agent
    - scaleops-recommender
    - scaleops-dashboard
    - scaleops-updater
    - scaleops-admissions
kind: ConfigMap

Step 3: Verify Configuration
Confirm the ConfigMap contains the ScaleOps exclusions before automating any workloads.