đ In Product Backlog
Support AKS as a Managed cluster
We will improve our managed cluster offering by adding Azure AKS to the list (today available only with the self-managed solution)
Alessandro Carrano About 20 hours ago
đ In Product Backlog
Support AKS as a Managed cluster
We will improve our managed cluster offering by adding Azure AKS to the list (today available only with the self-managed solution)
Alessandro Carrano About 20 hours ago
đ In Product Backlog
Display historical metrics for services
We will add a dedicated view to show some historical metrics for your services including: CPU RAM Network usage etc..
Alessandro Carrano About 20 hours ago
đ In Product Backlog
Display historical metrics for services
We will add a dedicated view to show some historical metrics for your services including: CPU RAM Network usage etc..
Alessandro Carrano About 20 hours ago
âī¸ In Development
Reuse container images across environments
When deploying an application from a container image, we have a mirroring process copying the image on the image registry attached to the cluster (more information here) we will improve this part and ensure we mirror only once the same image name / tag across all the environments, speeding up the deployment time
Alessandro Carrano 2 days ago
âī¸ In Development
Reuse container images across environments
When deploying an application from a container image, we have a mirroring process copying the image on the image registry attached to the cluster (more information here) we will improve this part and ensure we mirror only once the same image name / tag across all the environments, speeding up the deployment time
Alessandro Carrano 2 days ago
Allow list of IAM roles to access the Kubernetes cluster (AWS)
following the discussion on https://discuss.qovery.com/t/how-to-connect-to-aws-eks-using-iam-role/3472/9, it would be helpful to specify in the cluster settings one or more IAM roles that will be enabled to access the Kubernetes cluster (similar to what it is done with IAM users via the Admin group) As of now, the only solution is to modify the manually aws-auth configuration to enable them.
Pranas 2 days ago
Allow list of IAM roles to access the Kubernetes cluster (AWS)
following the discussion on https://discuss.qovery.com/t/how-to-connect-to-aws-eks-using-iam-role/3472/9, it would be helpful to specify in the cluster settings one or more IAM roles that will be enabled to access the Kubernetes cluster (similar to what it is done with IAM users via the Admin group) As of now, the only solution is to modify the manually aws-auth configuration to enable them.
Pranas 2 days ago
âī¸ In Development
Improve the way Managed Clusters are updated
We will review the way âManaged clustersâ are updated, adding a strict process between non-production and production clusters, maintenance windows etc..
Alessandro Carrano 17 days ago
âī¸ In Development
Improve the way Managed Clusters are updated
We will review the way âManaged clustersâ are updated, adding a strict process between non-production and production clusters, maintenance windows etc..
Alessandro Carrano 17 days ago
đ In Product Backlog
New product navigation
we will review the product navigation to ensure the different product features are well visible in the product: manage your production ephemeral environments etc..
Alessandro Carrano 17 days ago
đ In Product Backlog
New product navigation
we will review the product navigation to ensure the different product features are well visible in the product: manage your production ephemeral environments etc..
Alessandro Carrano 17 days ago
CLI: save contexts to be able to easily switch
Letâs say I have a staging and production environment, itâs currently a pain to run a shell in both envs back to back. It would be priceless to be able to save âfavoriteâ contexts to quickly be able to switch from one to another, and even better if we could pass the saved context as a flag to qovery shell commands Right now Iâm handling it with shell aliases but it would be great for it to be native
Adrien S 27 days ago
CLI: save contexts to be able to easily switch
Letâs say I have a staging and production environment, itâs currently a pain to run a shell in both envs back to back. It would be priceless to be able to save âfavoriteâ contexts to quickly be able to switch from one to another, and even better if we could pass the saved context as a flag to qovery shell commands Right now Iâm handling it with shell aliases but it would be great for it to be native
Adrien S 27 days ago
â Done
Display current instances
When checking the pods, same way we know what are the minimum and maximum instances, we would like to know total current running instances. Sometimes we have a lot of pods running and itâs difficult to count manually as there is no total anywhere in the table. I suggest make a counter in the right side, on the Resourcesâs section. Check screenshot.
Juan JosÊ CermeÃąo Portet About 2 months ago
â Done
Display current instances
When checking the pods, same way we know what are the minimum and maximum instances, we would like to know total current running instances. Sometimes we have a lot of pods running and itâs difficult to count manually as there is no total anywhere in the table. I suggest make a counter in the right side, on the Resourcesâs section. Check screenshot.
Juan JosÊ CermeÃąo Portet About 2 months ago
â Done
Kubectl/K9s available via the Qovery CLI
we will provide a way to get access to your Kubernetes managed cluster via the Qovery CLI and use the common tools like kubectl/K9s etc..
Alessandro Carrano About 2 months ago
â Done
Kubectl/K9s available via the Qovery CLI
we will provide a way to get access to your Kubernetes managed cluster via the Qovery CLI and use the common tools like kubectl/K9s etc..
Alessandro Carrano About 2 months ago
đ In Product Backlog
Show the list of environment linked to a cluster
We will provide a view displaying the list of environments linked to a cluster so that you will know which environment is running on it
Alessandro Carrano About 2 months ago
đ In Product Backlog
Show the list of environment linked to a cluster
We will provide a view displaying the list of environments linked to a cluster so that you will know which environment is running on it
Alessandro Carrano About 2 months ago
âī¸ In Development
Add Cluster status
We will introduce a new status for the cluster to give you a view of its healtiness. Today only the last deployment status is available
Alessandro Carrano About 2 months ago
âī¸ In Development
Add Cluster status
We will introduce a new status for the cluster to give you a view of its healtiness. Today only the last deployment status is available
Alessandro Carrano About 2 months ago
â Done
Show helm services linked to a Helm repository
We will allow you to retrieve the list of helm services which are using a specific helm repository as source for their deployment.
Alessandro Carrano 3 months ago
â Done
Show helm services linked to a Helm repository
We will allow you to retrieve the list of helm services which are using a specific helm repository as source for their deployment.
Alessandro Carrano 3 months ago
â Done
Show services linked to a container registry
We will allow you to retrieve the list of services which are using a specific container registry as source for their deployment
Alessandro Carrano 3 months ago
â Done
Show services linked to a container registry
We will allow you to retrieve the list of services which are using a specific container registry as source for their deployment
Alessandro Carrano 3 months ago
â Done
Improve service selection and domain customization for Helm charts
We will provide a way to retrieve automatically the list of services deployed by your helm charts so that it will be easier for you to expose them publicly (Today you have to manually enter the name of the service you want to expose)
Alessandro Carrano 3 months ago
â Done
Improve service selection and domain customization for Helm charts
We will provide a way to retrieve automatically the list of services deployed by your helm charts so that it will be easier for you to expose them publicly (Today you have to manually enter the name of the service you want to expose)
Alessandro Carrano 3 months ago
â Done
Streamline deployment for Terraform manifests
We will create a dedicated flow to deploy your Terraform manifests via the Qovery Lifecycle jobs
Alessandro Carrano 3 months ago
â Done
Streamline deployment for Terraform manifests
We will create a dedicated flow to deploy your Terraform manifests via the Qovery Lifecycle jobs
Alessandro Carrano 3 months ago
â Done
Streamline deployment for Cloudformation
We will create a dedicated flow to deploy your cloudformation template via the Qovery Lifecycle Jobs
Alessandro Carrano 3 months ago
â Done
Streamline deployment for Cloudformation
We will create a dedicated flow to deploy your cloudformation template via the Qovery Lifecycle Jobs
Alessandro Carrano 3 months ago
âī¸ In Development
Karpenter for production workloads (AWS Managed)
For your Qovery managed cluster on AWS, we will work on creating a version for Karpenter (the new node autoscaler) capable to support production workloads
Alessandro Carrano 3 months ago
âī¸ In Development
Karpenter for production workloads (AWS Managed)
For your Qovery managed cluster on AWS, we will work on creating a version for Karpenter (the new node autoscaler) capable to support production workloads
Alessandro Carrano 3 months ago
đ In Product Backlog
Track separately current vs target version of a service
Today the "version" of a service refers to the "target version" (the one we are trying to deploy on our cluster). But if a deployment is not triggered or it fails, this version is not representing what's actually available on the cluster We will separate the two versions making it clear the current vs target version of the application
Alessandro Carrano 3 months ago
đ In Product Backlog
Track separately current vs target version of a service
Today the "version" of a service refers to the "target version" (the one we are trying to deploy on our cluster). But if a deployment is not triggered or it fails, this version is not representing what's actually available on the cluster We will separate the two versions making it clear the current vs target version of the application
Alessandro Carrano 3 months ago