Questions

Hi There,

We want to deploy the latest update to production. But.. there are some RSA pair keys that we need to have when the release deployed to production. The RSA key files are not pushed into git repository for security reason.

So.. the idea is, we need those key pair to be available in our production server everytime we deploy the latest update into production. How we can do that? Similar like ENV variables, but this time the value is "file"

I have a cluster with two servers that are roughly in the same region. I have my production environment set up in such a way that all of the service containers (i.e., load balancer, discovery, and VPN) are located on one server and the main application containers are located on the other.

The "Neighbor Latency" panel says the latency between the servers is 8 ms.

With that being said, would it be better to have the service containers on the same server? Is there a standard practice for where the service containers should be deployed?

Any advice or insight would be appreciated!

How can I upload a profile picture to the community forum?

Is it possible to enable ipv4 (a.k.a. legacy mode networking) after the environment has been created?

Wondering how to setup VPC Peering into one of my environments, specifically want to use for RDS. Trying to keep infra as locked down as possible and don’t want RDS instances exposed public internet.

I am having trouble understanding the docs related to Discovery setup and deployment with a mix of HA and Manual.

The docs say:

"High Availability - mark the discovery service for high availability, Cycle will attempt to create 3 instances of discovery spread between the available infrastructure based on geographic distance and provider."

https://docs.cycle.io/reference/environments/services/discovery/#managing-discovery

--

If I manually deploy to a dedicated server for Discovery type services. Will the HA flag also deploy 2 other nodes for me or does the manual deployment over ride the HA?

The v1 load balancer is currently still in beta, as I've been using this for several months I was just wondering when it might be losing the beta tag.