You can scale a deployment up or down from the service overview using the scaling button in the header, or from the resources page.

Each replica will have the same resources as is configured for the service and Northflank will automatically load-balance traffic to each replica to ensure maximum availability.

Scaling a service to 0 replicas will make it unavailable. If you leave CI enabled the service will still build the latest commit to the linked repository, if you leave CD enabled it will also deploy that latest build when scaled up again.

You can select the number of replica sets your addon will use to increase availability, these replica sets contain a copy of the database to improve availability.

Addons can be scaled from the resources page. Addons cannot be scaled down, so any increase will be permanent.

Please note that the behaviour of scaled addons differs by type:

Addon typeBehaviour
MongoDBIf a primary node becomes unavailable one of the replica nodes will be promoted to primary, supporting read/write operations
Redis, Postgres, MySQLIf a primary node becomes unavailable only read operations will be supported by replica nodes. Write operations will only be restored once the primary node is restored.
MinIOA forward error correction algorithm is employed for optimal storage usage. Half of the replicas can become unavailable before the addon becomes inaccessible. You cannot scale MinIO replicas while it is running.

© 2021 Northflank Ltd. All rights reserved.