3 ms·

Agnost is an open source GitOps platform running on Kubernetes clusters

34 points by RyeCombinator 2y ago

paulglx 2y ago
Looks very interesting ! Is it not confusing to call k8s deployments "Containers", as they could be mixed up with Docker containers ?
- HoustonDad 2y ago
  [dead]
- from-nibly 2y ago
  I mean they are containers. They used to be docker containers, and I believe you can still choose to have them be docker containers.
  - shawnz 2y ago
    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.
  - antonyt 2y ago
    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/ https://agnost.dev/guides/containers/
- umit-cakmak 2y ago
  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.
deleted 2y ago
[deleted]
hhh 2y ago
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?
- umit-cakmak 2y ago
  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.

34 points by RyeCombinator 2y ago

Looks very interesting ! Is it not confusing to call k8s deployments "Containers", as they could be mixed up with Docker containers ?

HoustonDad 2y ago
[dead]
from-nibly 2y ago
I mean they are containers. They used to be docker containers, and I believe you can still choose to have them be docker containers.
- shawnz 2y ago
  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.
- antonyt 2y ago
  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/ https://agnost.dev/guides/containers/
umit-cakmak 2y ago
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.

deleted 2y ago

[deleted]

hhh 2y ago

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?

umit-cakmak 2y ago
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.