Container Groups are fundamental to the deployment process within the Salad Cloud Environment (SCE). They consist of a container image, hardware requirements, and a replica count, playing a crucial role in deploying your application on the Salad network. As the owner of the Container Group, you have the responsibility to manage it, while SCE takes care of running the group and maintaining the desired replica count.
- Container Registries: Specify the container image you want to run in the Container Group.
- Resource Requirements:
- Container Image name(Public or Private).
- Number of vCPUs (1-16): Define the desired number of virtual CPUs for your container.
- Memory (RAM) (1-30GB): Specify the amount of RAM required for your container.
- GPUs: Define the number of GPUs needed for your container
- Additional Parameters:
- Startup Probe: Set up a startup probe to check if the container is ready to accept traffic.
- Liveness Probe: Configure a liveness probe to check if the container is healthy.
- Networking: Choose between authentication or no authentication for external requests and port number for enabling networking inside of container.
- External Logging Service: Optionally configure an external logging service for container logs.
- Environment Variables: Define environment variables to customize your container's environment.
The container configuration page offers an auto-start feature. By default, this feature is enabled, and it automatically starts the container when the image is pulled. This ensures that your containers are always up to date and readily available.
Note: For detailed instructions on deploying containers, please refer to our "Deploy Container Group" documentation.
Container Group actions allow you to create, manage, and modify your container deployments effectively. To access the container group actions you first need to deploy a container.
- Create : Create a new Container Group. When created, it is not yet running on nodes.
- Start : Initiate a deployment of the Container Group on the Salad network.
- Stop: Stop the current deployment, pausing all active Container Instances. Stopped Container Groups can be started again.
- Refresh: Refresh allows you to update the status and information of a Container Group without making significant changes to the group itself.
- Duplicate: Create a copy of an existing Container Group, allowing for easy replication of settings and configurations.
- Edit (Name and Replica Count): Update the name and replica count of a Container Group once it has been created.
- Delete: Delete a Container Group and all associated information. This action is irreversible.
Updated about 1 month ago