Edit me

Managing Karpenter Configurations With nOps GitOps Support

With GitOps support, you can now manage Karpenter configurations either through the nOps dashboard, the CLI, or IaC tools (such as Terraform and CloudFormation). nOps automatically detects and syncs any changes to onboarded NodePools and NodeClasses, allowing you to automatically maintain all your configurations seamlessly through your chosen tools.


  1. You must have onboarded at least one Kubernetes cluster to nOps Copilot for EKS.

  2. The nOps Karpenter agent must be on version 0.4.1 or later.

    a. For a prefilled command, please visit the cluster details page: Configure nOps Karpenter Agent on EKS

Overview of GitOps Support

  1. nOps automatically scans and displays all of your NodeClass and NodePool objects in the dashboard.

    a. NodeClasses and NodePools created by nOps are marked with an icon to differentiate them from NodeClasses and NodePools that were created outside of nOps. These detected NodeClasses and NodePool objects are not automatically managed by nOps, but their configuration can be viewed in the application.

    nOps dashboard showing two NodeClasses created and managed by nOps, a NodeClass created outside of nOps managed by nOps, and a NodeClass created outside of nOps and not managed by nOps

  2. A new attribute imported_by: nops defines whether nOps will manage and update your configurations for a NodeClass or NodePool for Spot optimization. If you want nOps to manage a NodeClass or NodePool that was created outside of nOps, add the key:value imported_by: nops under metadata.annotations in your source code.

  3. Once the attribute is added, the object will be automatically detected in approximately one minute.

  4. Once detection has taken place, nOps will begin to manage the configuration for your NodePool and automatically optimize workloads being provisioned by it. You are now able to edit the NodeClass from either the nOps UI or your source code, and changes will be automatically synced.

    a. The nOps agent continually monitors the Karpenter resources annotated with imported_by: nops and sends any changes via API to our application. If you edit a NodeClass or a NodePool using the nOps dashboard, the changes will likewise be propagated automatically to your cluster by the nOps agent and API.

Managing Resources With Karpenter GitOps Support
Configuring ASGs by Tag
nOps Copilot-Managed ASGs
Compute Copilot For ASG Support Matrix
Onboarding your Autoscaling Groups to nOps Compute Copilot
Onboarding your Autoscaling Groups to nOps Compute Copilot via Stackset
Configure Commitment Management
Compute Copilot for ECS
Onboarding your EKS clusters to Copilot for EKS Cluster Autoscaler
EKS Provisioner Examples
Compute Copilot for EKS - Karpenter Beta Support
Onboarding your EKS clusters to Compute Copilot for EKS Karpenter
Our Approach to Optimizing Commitment Utilization
Compute Copilot Spot Instance Reliability SLA
YAML file for nOps Commitment Management
Minimum IAM permissions for the nOps platform
IAM permissions for the nOps platform
IAM permissions for Essentials
Onboarding AWS Linked Accounts
Onboarding Multiple AWS Linked Accounts with CloudFormation
Onboarding AWS with Manual Setup-Contact Us
Service Control Policies
Onboarding AWS with Automatic Setup
Onboarding AWS with 1-click CloudFormation
AWS SSO Integration
Azure SSO Integration
SSO Integration
Okta SSO Integration
OneLogin SSO Integration
Back to top       Home
Tags: copilot