Easily connect to your cluster, More cluster info available, Alpha/beta phase on Azure, New support tool
Hello Team,
Check out this week’s changelog for exciting updates and enhancements from our team! 🚀
#Access your Kubernetes cluster directly from the Qovery console
Admins can now connect directly to their Kubernetes cluster from the Qovery console. Just head to the cluster page, hit the “Connect” button, and you’ll be dropped into a pod with kubectl, k9s, and other tools ready to go.
The objective? We want to simplify the life of cluster admins. No need to download kubeconfigs, install tools, or worry about credentials. It’s now easier and faster to check what’s going on in your cluster, right from the browser.
#Additional cluster info available in the Terraform provider and environment variables
We’ve added more Kubernetes cluster metadata both in our Terraform provider and as environment variables:
- The cloud provider cluster name (env var QOVERY_KUBERNETES_CLUSTER_NAME)
- The cluster OIDC issuer
- The cluster ARN
- The cluster VPC ID (env var QOVERY_KUBERNETES_CLUSTER_VPC_ID)
The objective? Make it easier for anyone to use the cluster information at different levels:
- Simplify IAC configuration with our Terraform provider: managing the cluster setup without that information was a pain and required running custom scripts within the Terraform manifest
- Simplify the deployment of managed cloud provider services: easily retrieve the VPC information so that the resource can be deployed within the same VPC of the cluster without having to create a separate one.
#Azure (AKS) managed solution - Looking for Alpha and future Beta testers
We’re launching a fully Qovery-managed AKS (Azure Kubernetes Service) experience. This brings all Qovery capabilities to Azure without the need to manage the cluster yourself via our self-managed solution.
If you need to run your workload on Azure in a fully managed, scalable and secure way, get in touch with us! (via Slack or the support widget on our website)
We are ready to launch our alpha phase before having a public beta, and thus we are looking for customers willing to collaborate with us up to the official release.
#Customer support - Now fully powered by Pylon
We’ve completed the migration to Pylon, our new support system. All console requests now go through the same platform we use for Slack and email.
The objective?
Providing the best customer support has been at the core of our company since day 1. Making it scale with the increasing number of customers has been a challenging task, and we had to adapt our internal tools to make it happen. Thanks to the Pylon integration, we can now provide the best support experience across different channels (Slack, email or our console)
#Minor Changes:
- CLI - added "list commands" action: it allows you to discover the available commands on our CLI.
- Improved toast message in case of variable conflict: when adding a variable which already exists, you now get a message providing you with the name and the location of the conflicting variable.
For the latest news and upcoming features, remember to check out changelog.qovery.com.
As always, we appreciate your feedback and support.
Happy Deploying!
The Qovery Team 🚀