What's the advantage of this over something like Argo? Is it the UI and the fact that it can do some container building stuff?
Hi,
This is Umit the maker of Agnost. It indeed does container building. ArgoCD and Flux are great GitOps tools that focus on automating the deployment of Kubernetes resources based on changes in a Git repository. They do not build Docker images or push them to a container registry. Instead, they deploy pre-built images to Kubernetes by syncing the state of the cluster with the manifests defined in a Git repository. On the other hand, Agnost builds and deploys images to the Kubernetes cluster and updates the image tags of your Kubernetes resources when a build and deploy pipeline is triggered.
Looks very interesting !
Is it not confusing to call k8s deployments "Containers", as they could be mixed up with Docker containers ?
I mean they are containers. They used to be docker containers, and I believe you can still choose to have them be docker containers.
Strictly speaking, k8s deployments describe a number of pods, and pods describe a number of containers. So creating a deployment in k8s could result in the creation of many containers as a result.
Parent is referring to Agnost's own concept of Containers, which are a different concept and further overloading the term. I agree with their take that this is confusing. Your Agnost Container is an abstraction over several K8S abstractions over actual containers.
https://agnost.dev/guides/containers/
Hi there,
This is Umit, the maker of Agnost. I think you are right it can be confusing. By container we actually mean resources such as deployments, statefulsets, cronjobs. It is not related to containers in a pod.