Terms/Misc

Common Terms for Exopods and Container Deployment

Deployment Name

• The unique name given to your deployment, used to identify the specific instance of your application or service running in the container. You can name it as per your choice.

Repo URL/Tag

• Repo URL: The URL of the repository where your container image is stored. It can be a public or private registry.

• Tag: A label that specifies the version or variant of the container image. It usually defaults to latest if not specified.

Private Registry

• A secure, non-public container registry where images are stored. It requires authentication (credentials) to pull images. Examples include AWS ECR, JFrog, or Docker Hub (private repos).

Internal Endpoint

• A network address used to access services within the container or private network. It’s typically not exposed to the public and is accessible only within the internal network or between containers.

Public Endpoint

• A publicly accessible address (URL or IP) that allows external users to access your deployed service. This is used to interact with your service over the internet.

Port

• A communication endpoint in networking. In container deployments, it specifies the port on which your application will listen for incoming traffic (e.g., port 80 for HTTP, port 443 for HTTPS).

Commands

• Instructions executed inside the container when the container starts. These are typically used to start the application, run scripts, or initialize services.

Arguments

• Additional parameters passed to the commands to modify the execution of the program or scripts running inside the container. They allow for dynamic configurations at runtime.

Environment Variables

• Key-value pairs that define settings or configurations for the application running inside the container. They are used to manage settings like database URLs, API keys, or credentials without hardcoding them into the application.