Hello, and welcome to our January release notes. This month’s changes bring more visibility to your Kubernetes metrics using dashboards, add new ways to manage your config files, and provide an option for graphic-intensive workloads on GKE.
If you haven’t already, go check out our blog on the 7 cloud trends for 2023.
NEW: GitMerge conflict handling
Previously, any manual edits to the configuration files on your repo would be over-written when you apply changes through Argonaut. This is no longer the case. With the new three-way GitMerge feature, we compare the contents of the old version of the file, the current version of the file, and the proposed version of the file. And merge only if there is no conflict.
When a conflict exists, we return an error and raise a PR so you can fix them manually without losing any of your changes. It means users can manually make any changes to the
art.yaml, workflows, or any other Argonaut-created files in your repo. This works on GitHub and GitLab.
NEW: Dashboard tab
The new Dashboard tab in your clusters gives you the ability to interact with k9s CLI. Users can see a top-level view of their pods, jobs, and events. Dive into cluster resource dependencies. Check pod status, resource usage, and more!
NEW: App Metrics Charts for k8s
All your Kubernetes app metrics are now extracted using Prometheus and available for you to view right from your App’s Logs screen. The newly added charts show the selected app's CPU, Memory, Network, and Storage usage. The time range can vary between past 1 minute to past 4 hours, and the refresh interval can be set between 5 seconds and 60 seconds.
This is available for apps running on both EKS and GKE. Go to your
Environment > Cluster > App > Logs to access your app’s metrics.
Note: Prometheus is one of the essential add-on apps, and it is added by default as part of every cluster created using Argonaut.
NEW: Create an environment inline
Users can now create a new environment right from Argonaut’s environment page. Just click on the
Environment + button on the top right of your environment list. This opens up a new environment create form, in-line, and right below your existing environments.
NEW: Enable GPU on GKE
By Subham, Prashant
Users can now enable GPU on GKE while creating new node pools. This allows the user to run more GPU-intensive tasks for their applications. Only the GPUs available across the three AZs (A, B, and C) in your environment’s region will be shown. You also have new fields to assign accelerator type and accelerator count. This is only available with certain machine types. Please check the GKE documentation for information on regions and requesting GPU quotas.
ADDED: Multiple AWS account support
By Subham, Wahal
Argonaut users can now connect multiple AWS accounts to their Argonaut account. You can add additional accounts by going to clicking on the profile icon on the top right
Settings > Cloud Connect > Account + > Create AWS integration.
This will automatically set up an Argonaut IAM user to create and manage the infrastructure automagically. Provide IAM role to Argonaut.
Note: Duplicate AWS integrations with the same Account ID are not supported!
CHANGED: Lambda deployments page
The deployment page for AWS Lambdas has also been improved by including sorting logs and history by date, etc.
Other minor changes and fixes:
- The environments table now displays listing account ID (AWS) / Project name (GCP)
- The infra table now also includes the cluster version of your EKS clusters
- Gitrepo secrets fallback option available on the update screen
- Automatic scroll to make sure the error message is visible
- Styling changes in drop-down menus