Feature Ideas

Trending
  1. Point to branch head when cloning env (manual or automatic preview)

    When cloning an environment (manually or via the preview env feature) you should decide whether the cloned env should have the branch updated to the latest commit or if it should be a pure clone of the environment used as blueprint.

    Alessandro Carrano
    #Improvement πŸ‘

    0

  2. Improve build speed - share images across environments

    We will review our image mirroring mechanism (https://hub.qovery.com/docs/using-qovery/deployment/image-mirroring/) to share the built images across environments if they use the same repository and commit id. This will speed up the deployment when cloning environments manually or via the preview environment feature.

    Alessandro Carrano
    #Improvement πŸ‘

    0

  3. Cron Job build error should not cancel environment deployment

    I have an environment that has Start & Stop enabled, and a cron job build failed, but the whole environment deployment was cancelled. A cron job build error should not cancel the whole environment.

    Moises A
    #Improvement πŸ‘

    0

  4. Bulk update and deploy applications based on their branch without specifying the app/environments

    (created from https://discuss.qovery.com/t/container-registry-deploy-multiple-environments/2476) Provide a way to bulk update and deploy a set of applications based on their branch, without having to specify the app or the envs where they are running. For example: I have 3 applications having the same branch A and I want to update the 3 to a specific commit id. I can just send a request saying to update all the services on branch A to the commid id X (similar to what we do with the auto-deploy feature via the git providers) Example via the CLI: My issue is in trying to deploy to several environments all at once. I imagine that I could do something like this: qovery application deploy --organization --project --environment ", , " --applications --commit-id --watch However, every time I would add a new environment, I would need to remember to update my Github Action. And if I wanted to trigger on different branches I would need multiple actions and separate lists of my environments. Is there a better way to trigger deployments for each individual Qovery environment based on when a particular Github branch is updated?

    Alessandro Carrano
    #Feature πŸ”₯

    0

  5. S3 storage

    Sometimes I may need to store files on S3. Eg: I have a service that received images from users, I need to save the images and expose them publicly.

    albane t
    #Feature πŸ”₯

    5

  6. Support Azure

    Support Azure to deploy applications

    albane t
    #Feature πŸ”₯

    5

  7. Application monitoring and logging with Grafana (Prometheus + Loki)

    Grafana, Prometheus, and Loki are already installed on the cluster for internal Qovery use. I would like to be able to set up Prometheus to fetch metrics from our applications and use Grafana to analyze them. Also it would be nice to have access to Grafana for more powerful log querying from Loki.

    Pranas
    #Feature πŸ”₯#Improvement πŸ‘

    3

  8. Datadog one click install

    Native support of Datadog as a monitoring platform in Qovery. Important Note: Datadog is already supported in Qovery but we want to provide better integration. Contact us or put a comment if you have any questions.

    albane t
    #Feature πŸ”₯

    1

  9. Support Docker Compose file

    Support Docker Compose file to configure a Qovery environment and deploy complete apps.

    albane t
    #Feature πŸ”₯

    1

  10. Customize labels/tags on resources

    Add the possibility to add custom tags / labels on the resource managed by Qovery that should be replicated on the cloud provider entities (clusters, pods, managed databases etc..). This will make it more simple to monitor those resources via the standard monitoring tools (datadog etc..)

    Alessandro Carrano

    3

  11. Manage database Backups

    See and create backups for your databases

    albane t
    #Feature πŸ”₯

    0

  12. Dark mode

    Vote fore all views in dark

    albane t
    #Improvement πŸ‘

    0

  13. Support spot instances (GCP + AWS)

    It would be helpful if there was spot instance support for EKS clusters. We use spot instances in our non-critical clusters (dev and testing). We use eksctl to create spot node groups as follows: managedNodeGroups: name: my-new-asg instanceTypes: [β€œc5.2xlarge”, β€œc5d.2xlarge”, β€œc5n.2xlarge”, …] spot: true This is nice because it's all managed within our AWS account, and we don't have to signup for external services.

    Kyle F

    3

  14. Support Hetzner (Cloud Provider)

    Support Hetzner to deploy applications.

    Utkarsh K
    #Feature πŸ”₯

    1

  15. Integrate Karpenter as autoscaler for AWS EKS

    Offer Karpenter as the node autoscaler for AWS clusters.

    Guillaume G
    #Improvement πŸ‘

    2