More on ProjectEnv:

Projects are related to several other Sleakops entities like environments and services. The union of a project with an environment makes a namespace for the cluster and this is one of the main SleakOps entities, we call it ProjectEnv.

If you create a ProjectEnv SleakOps creates an AWS ECR that is where we save all the charts and its templates and also the build images that we use to later do the Deployments on the EKS Cluster. As previously stated, we consider this ProjectEnv a Cluster Namespace where we allocate all the services that are deployed on the Kubernetes Deployment.

At this point we analyze with simple tools the correctness of your Dockerfile and how you are configurating it and also we Build an Image of that Dockerfile that are later used to deploy all your services, for this we use Kaniko, for more info of this third party tool checks its Documentation . When you submit the form we run the first build, more info here .

Something else that we manage as directly related to the ProjectEnv is a Service Account , it is a Kubernetes resource that allows us to manage the permissions of the resources we create inside the cluster so they are able to connect with the AWS services you create.

Kubernetes Volumes

In some cases you need that many of your Services use a unique storage volume that is found inside the Kubernetes cluster. For this implementation we use the Kubernetes Volumes . These volumes are storage units allocated inside the cluster that can be used from any of its pods/containers. To create them you can do it by editing a ProjectEnv or on its creation, when you enable the volumes you can start adding them by defining its mount path and the storage capacity each has. As we work on AWS we install and use the EFS CSI Driver to use EFS file systems as EKS Volumes.

An example of how you create a Volume would be: