Feature Ideas

Trending
  1. Support spot instances

    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

  2. Add environment TTL

    We will let you define a TTL for your environment after which the environment will be automatically stopped and deleted. It will make sure that your environments won't run for nothing and you keep control on your cloud cost

    Alessandro Carrano
    #Feature πŸ”₯

    0

  3. Cluster usage view

    We will deliver a new cluster view allowing you to better understand the current cluster consumption and what is consuming the most

    Alessandro Carrano
    #Feature πŸ”₯

    0

  4. Allow to trigger a deployment if another one is already ongoing on the same environment

    Today you can trigger only one deployment at a time within one environment. If a deployment is ongoing on the environment and you try to trigger a second deployment, you will get an error message telling you that the operation is not allowed (since another deployment is ongoing) The objective will be to allow you to trigger other deployments if there's one already ongoing. At the minimum we will provide the possibility to queue the deployments without having you wait for the deployment to end, improvements could be done in the future to parallelize the operations (if the deployment is not on the same service)

    Guillaume G
    #Improvement πŸ‘

    2

  5. Provide stats on deployment times

    We will provide more information on the deployment of your applications by providing you with the time that was necessary to: Pull the source code Build the app Deploy the app The information will be available on both the deployment tab and the deployment log screens

    Alessandro Carrano
    #Improvement πŸ‘

    0

  6. Github Actions

    create some github actions for the marketplace: 1: that installs and runs commands from the qovery cli, letting you specifiy the version and commands 2: one that populates a pull request page with details from qovery around the deployed solution (ie being to give the url of a deployed service)

    Stephen B

    0

  7. Create Preview Environment pointing to any branch

    Right now Preview Environments can only be triggered when the PR is to the branch of the service on the Blueprint environment. Example: app1 -> development, app2 -> master, app3 -> development. If I create a PR in app1 from feature -> development it will let me create a Preview Environment. If I create a PR in app1 from feature -> master it will not let me create a Preview Environment. Both cases it will have app1 with the branch feature for the Preview Environment and the rest as they are configured. It does not really matter where the PR is pointing to, the branch from where the PR was created is what it needs to be tested.

    Moises A
    #Improvement πŸ‘

    0

  8. Manually Stop Preview Environment in Pull Request Comment

    On top of the TTL feature, it would be nice to be able to leave a comment on the Pull Request to destroy the Preview Environment (as when merged or declined). In our case we have Preview Environments created manually with the /qovery preview xxx-xxxx command. But in many cases a bug is discovered in the Preview Environment and there is no need to have the environment running because it may take hours/days to solve. Being able to have a command like /qovery preview destroy xxx-xxxx would be very helpful instead of having to close the pull request.

    Moises A
    #Feature πŸ”₯#Improvement πŸ‘

    0

  9. Built-in Qovery Docker with qovery CLI installed

    Currently to create a lifecycle job, the only option is to use Docker mode where you specify a Dockerfile. With this in mind if I have a script that use the Qovery CLI the only option I see available is either have a Dockerfile that installs the CLI or use FROM ghcr.io/qovery/qovery-cli:latest It would be great if there was a builtin Docker image to choose from that has the qovery CLI installed, so the process is faster and no need to build it, that way we could just run a script like #!/bin/sh set -e qovery application domain create -n "app" --domain api.preview-$QOVERY_PULL_REQUEST_ID-domain.com and only configure the CMD arguments to run the bash script like ["script.sh"] in the Qovery Console.

    Moises A
    #Feature πŸ”₯

    0

  10. 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

  11. Support Azure

    Support Azure to deploy applications

    albane t
    #Feature πŸ”₯

    5

  12. 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

  13. 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

  14. Support Docker Compose file

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

    albane t
    #Feature πŸ”₯

    1

  15. 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