184 results found
-
1 vote
-
Basic analytics for servers
I think it would be great to install a few basic analytics for our server to track main KPI so that we know we we should scale or down scale servers.
- CPU Load
- CPU%
- Memory%
- Disk space on Postgres2 votes -
Add Support for Pod Affinity/Anti-Affinity
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 -
Allow to set optional ipv4 on Hetzner
Hetzner announced the ability to disable ipv4 on cloud instances, which would save an extra 50 cents on instances. It'd be nice to be able to disable them on internal only instances (eg. database, workers, etc)
3 votes -
Add server tags as liquid template properties in HAProxy CustomConfig
I'd like to be able to create multiple backends in my HAProxy configuration based on the tags that are attached to servers. This would enable me to create path based routing so that I can have web servers solely dedicated to API requests.
1 vote -
Add Preview Deployments in Maestro
It would be awesome to have the ability to set up Preview Deployments as you can with Rails. We're primarily a nodejs shop and this would be invaluable to speeding up our dev/qa pipeline. Source: https://help.cloud66.com/rails/how-to-guides/deployment/preview-deployments.html
4 votes -
Allow database groups to be renamed and allow dashes/underscores in group names
We can currently rename stacks but cannot rename database groups! Also for some reason dash and underscore are not acceptable characters in a database group name.
3 votes -
Improve CI/CD tooling support
The current solution for CI/CD integration (e.g. GitLab) is to use curl to hit a redeploy hook that sends a signal to Cloud66 for deploying the application. This doesn't integrate very well with pipeline flows, since there's no guarantee the deploy will succeed. Meanwhile the pipeline is marked as passed, but in reality the app failed to deploy.
The CX Toolbelt does offer an option to --listen, which is great. However, this Toolbelt is clearly intended for manual use and not by something like Docker or a CI pipeline script. This is possible but not officially supported, and the setup…
1 vote -
Share support tickets among team
When a support ticket is created, we would like it to be able to be tracked by multiple developers, not just the user that created it. That means having the tickets show up on the UI (with a way to read them, preferably), and emails being sent to everyone on the support list.
3 votes -
Reducing git repo pull time
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 -
VPC configuration through manifest when using Digital Ocean
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 -
log rotation with file size
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 voteThank 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.
-
Provide Anycable integration support
Provide Anycable integration support. Tutorial about setting the gRPC server and serving it on a separate port
4 votes -
caching dependencies on scaling up new servers
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 -
JSON output for all cx commands
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 -
SSH identity federation (cx ssh) without the app deployment part
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 -
Deploy previews based on pull request labels
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 -
Deploy previews based on pull request source branch
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-123and my source pattern isfeature*.1 vote -
Instant and Full Rollbacks
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 -
Add AWS load balancer response codes to httpchk
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
- Don't see your idea?