General

General

Categories

  1. Currently with MaestroV2, our pods with replicas are being deployed on the same nodes at times which defeats the purpose of our highly available pods running on a single node in our multi-node cluster.

    I'm proposing adding a feature to Maestro to incorporate the Kubernetes concept of Pod Affinity/Anti-Affinity to allow Kubernetes to schedule pods to separate nodes based on what pods are already scheduled on the nodes.

    Here is the documentation from Kubernetes on the Pod Affinity/Anti-Affinity concept: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity

    42 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. It looks like repo are re-cloned at every server deployment instead of just a pull. We need a way to change this behaviour to remove our 3 minutes waiting time at every server deployment.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. At the moment all droplets created within Digital Ocean are placed onto the default VPC. This makes it difficult to provide network segregation if multiple stacks are deployed onto the same Digital Ocean cloud.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Please add an option for Log rotation by file size.Like below example
    /var/log/apache2/* {
    weekly
    rotate 3
    size 10M
    compress
    delaycompress
    }

    where size is specified 10M

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thank you for your feedback. This request has been initially reviewed and is under consideration. Further updates will be provided as soon as there is substantial update.

  5. We should be able to easily cache bundler/yarn/assets dependencies on our new scaled up servers (on new builds, as we do in our deployments using capistrano)

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Provide Anycable integration support. Tutorial about setting the gRPC server and serving it on a separate port

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. The slack notification when replication fails provides no context, and there's nothing in the UI or logs to troubleshoot, so I had replication to slave intermittently failing for days with no ability to directly see what the problem was (and if I didn't have slack, would not have known about it at all)

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. The Cloud66 API returns JSON for every endpoint, while cx primarily outputs formatted text. As a cx user, I would like to have optional JSON output instead of formatted text so I can use cx output more easily in scripts.

    One approach I would like to offer is a --output=json flag for each command. Thank you!

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. The "cx ssh" command is pretty useful for SSH identity management, since we manage in a central place who is able to login on each application stack. I also saw that command opens the SSH port on demand.

    But for now, this "cx command" only applies to servers fully managed by Cloud66, which includes the application deployment part.

    Feature request: Please allow the installation of the cx_agent on Ubuntu servers without the app deployment part, at a favourable price.

    Thanks so much the Cloud66 team for your assistance.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. When configuring preview deployments based on pull requests, filter by label(s).

    E.g. if a PR is opened (or labels are added or removed from an existing PR), if it contains certain labels, deploy a preview.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Currently you can only filter on the target branch, but it'd be nice to be able to filter on the source branch name within the PR config.

    E.g. have a PR config with:
    - source branch pattern (the new option I'm suggesting)
    - target branch pattern (currently the only option)

    Then I could open a PR against the stack branch (e.g. staging), but only have it spin up a preview environment if my source branch is e.g. feature-123 and my source pattern is feature*.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Instead of running a full rebuild which can take a very long time when things are broken, use the last build. Capistrano stores the builds and it completely defeats the purpose of their existence if we never use them. It would take a few seconds at most to rollback a problem vs waiting for an entire new build. For our stack that's over 10 minutes of downtime.

    My proposed solution based on some chats in Slack is to have both an Instant and Full Rollback option since I was told some stacks have deploy hooks that need to be rerun.…

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. This would save time so as not to have to go to the AWS UI to configure these separately. On the same note "Redirect HTTP to HTTPS" option should include an expected response option. Meaning if my server is expected to send anything other than a 200 response to the check, the server will return as healthy. For example, a 301 or 302.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Increasing the number of groups in a rolling deployment would be more feasible for certain deployments. It would also allow us to run better than half capacity.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Whenever we clone a cloud machine, we should have a way to copy the jobs as well. Or export the job and reimport it. It'd save us alot of time when we are trying to replicate the production's site.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. We have a lot of sidekiq queues that would benefit from this.

    For example, we have 6 pods running for sidekiq which are only used between 00:00-06:00 and we could scale up other parts of our app after these jobs have completed but right now I would have to manually do this.

    https://github.com/kedacore/keda

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. The API is very handy when you need to automate stuff but the documentation is not up to date. I would rather not have to bother the support with questions regarding missing things in the docs.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Add an option to automate firewall rules installation through manifest.yml file
    e.g.
    staging:
    firewall_rules:
    from: 127.0.0.1/16
    to: 123.123.123.123
    protocol: tcp
    port: 22

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. As per the Ruby on Rails guide for a multi db setup;

    the username for the writers and replicas should be different, and the replica user's permissions should be set to only read and not write.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Allow deployment to Ubuntu 20.04

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 9 10
  • Don't see your idea?