Introducing GitOps support for Compute Copilot for Karpenter
Manage nOps NodePools and NodeClasses centrally via your preferred Infrastructure-as-Code (IAC) tools
nOps Compute Copilot now offers enhanced capabilities to fine-tune your Karpenter configurations automatically and continuously for better performance at lower costs. Previously, managing Karpenter NodePools and NodeClasses via nOps required using our user interface. However, many users prefer to manage their Karpenter configurations via IAC tools.
New GitOps Support For Improved Efficiency
With GitOps support, you can now leverage Compute Copilot without managing Karpenter configurations from the nOps dashboard. Changes to NodePools and NodeClasses made externally via CLI or IaC tools (Terraform, CloudFormation…), are now automatically detected and synced to the nOps backend. This enhancement allows you to maintain all your configurations cohesively through your chosen tools, eliminating the need for separate management on the nOps dashboard.
This feature is particularly valuable for those overseeing multiple clusters, facilitating bulk changes across various configurations effortlessly. By using IaC solutions, you can scale operations and reduce manual effort, improving operational efficiency.
How it Works
GitOps support is available for nOps Compute Copilot agent versions 0.4.1 and higher. To enable GitOps support, simply add the metadata annotation ‘imported_by:nops’ in a key:value approach to any NodePools or NodeClasses you wish to import to nOps. The agent will recognize this label, automatically and continuously syncing these objects to the backend, including any future updates.
For more information on how GitOps support works, consult the documentation
How to Get Started
To start using GitOps support, navigate to the Compute Copilot dashboard and update your agents to the latest version. Then, to import a NodePool or a NodeClass to nOps, just add a ‘imported_by:nops’ (key:value) in each resource that you’d like to import under ‘metadata.annotations’ object.
On the very next agent sync, the resources will be imported in nOps, and you'll be leveraging the Spot improvements. You can even choose to manage your configurations using our YAML Editor in the app.
We're Here to Help
Have questions? Need help getting started? Our dedicated support team is here for you. Simply reach out to your Customer Success Manager or visit our Help Center. If you’re not sure who your CSM is, send our Support Team an email
New to nOps?
You can get started with nOps by signing up for a free account or scheduling a demo with one of our AWS experts.