Key Concepts

Understanding the key concepts in Agnost Studio is crucial for effective container management. Agnost Studio is the management console where you create, manage, and monitor your containers.

• Cluster: The cluster is the top-level entity representing the Agnost deployment in your Kubernetes cluster.
• Organization: In Agnost, you start creating your projects under organizations. The organization is the logical grouping of your projects. You can think of organizations like a company, client, or functional unit.
• Project: The project is the fundamental entity in an Agnost cluster. Each project can have its team, meaning you can assign different roles to team members and collaboratively work on a project as a team. Each project can also have one or more environments where you deploy your applications (e.g., containers).
• Environment: You can think of the environment as branches in a git repository. A project can have many environments: production, staging, development, test, etc. Please note that each environment has its own Kubernetes namespace, which ensures the isolation of different containers and services. You deploy your applications in project environments.
• Container: As its name implies, these are the resources you create in your project environments. A container can be a Kubernetes deployment, stateful set, or cron job. For example, in your development environment, you can create three containers, a deployment backend of your app, another for the frontend, and a stateful set database.

Note

Please do not confuse the container terminology used in Agnost with that used in Kubernetes pods. In Agnost, containers define a higher-level entity, a resource, that covers deployments, stateful sets, and cron jobs.