This month, we bring you the first set of updates to our user interface - compact components, a better user flow, and more. Other updates this month include better version control, GCP integration using service key, and backend updates that have been much requested. Read on to find out more!
NEW - Argonaut UI
Our new settings page provides more context for your cloud and Git connections. It makes it even easier to access your Argonaut Org and billing details. Managing version control connections, cloud integrations, and billing is simpler. Your dark/light mode setting and profile settings - password, 2FA, SSO can be accessed through your profile icon on the top.
Our new app list page has three tabs - Logs, Deployments, and Configurations. The Logs tab contains pod Logs. The Deployments tab shows the history of your deployments along with their respective commit IDs. The Configurations tab has two sections Build and Deploy. Build consists of build options such as selecting a run time and adding build details. In Deploy, you can add Network Services, resource requests and limits, secret files and deploy. Using this you can also make edits to an existing deployment.
💡 Note: Lambda apps do not have a Logs section. Their deployment and cloud watch logs can be found under the
Deploymentstab.
ADDED - GCP integration using the service key
You can now also integrate your GCP account using your service account key. This integration is limited to your project and does not work as a GCP organization integration.
ADDED - Multiple node groups support in GCP (GKE)
The GKE cluster creation flow now supports multiple nodegroups. This enables services where heterogeneous instance types are required - like GPUs, x86-64, and ARM cores - all in one cluster. The specific nodegroups can be targeted by the applications through the art.yaml file configuration. Support in AWS is coming soon.
CHANGED - Version Control
We now list all GitHub and GitLab entities like organizations, repos, branches, etc. We handle responses better in situations when an integration does not exist. Git update is disabled when integration doesn’t exist.
CHANGED - List of applications show the undeployed apps too
The list of applications excluded the ones which were currently pending first successful deployment. This behavior is modified to enable easier app creation UX, especially for secret management and deployment settings.
Other improvements and fixes
- Hide/unhide secrets
- Gitlab multi-env support to allow multiple workflows
- More readable texts during environment error
- Inline environment name validation
- Secrets get reset when the hostname is changed from the UI
- Fixed incorrect GKE pricing, now cluster maintenance fee is also included