Devtron

- The CI/CD process is very well executed, easy to use and understand. With a few extra tweaks like using BUILDX it's very fast too. - It's tools for managing helm charts is a blessing. It's very easy to push new charts and manage them from devtron chart store, and upgrading versions is easier too because you can compare your values.yaml file and pass over only the values that are relevant while preserving your own (such as copying the new image value without overwriting the whole thing). - debugging - viewing pod logs, bashing into them, ephemeral containers - it's all extremely accessible and easy to use, overcomes the confusing complexity of using kubectl commands, letting the team work with the cluster in a natural way and without having to manage RBAC on the cluster directly. Just wonderful stuff, really.

it gives a consolidated ui on our applications and clusters of kubernetes

Devtron has a rich set of features be it Kubernetes-native CI/CD pipelines, approval policies or even the plugin policies. It has all the necessary features in place to make life easier working on Kubernetes but along with that it has the necessary policies and guardrails as well which allows me to set boundaries where developers can work around without hampering my production environment. It has made the application management on Kubernetes so easy that even a novice in Kubernetes can work easily without depending on DevOps teams or Kubernetes experts.

There are a few nitpicks here and there, some that I have raised with the team themselves. - Devtron uses some old tools, only recently upgraded the postgresDB from version 9 to 14, and still using ArgoCD version 2.5.2 as of the time of this writing. - The weird spots where they are highly opinionated. While the tool is fantastic and mostly very flexible, there are some things that are weirdly limited - if you create an application, once you select a chart you cannot change it, you can't rename apps, every workflow is always the same pieces, without much room for setting up different steps (for example, while an app can use a build from a different app, it still has the build step included, even though it should be irrelevant). Most of these have reasonable workarounds, but they make some things weirdly limiting. - Setting up mono-repos is not the best, you can't set up a single source for code, you have to re-import the same source every time (but you do have control over what directories to listen to, so it's not completely unsupported and it works fine for us) - Devtron configures their environments as namepsacecluster. This probably works for some clients, but for us it's a bit of a weird setup because every time we want a microservice to use a different namespace we have to create a new environment in the settings page. It's again, a weird opinionated decision that stands out with the rest of the platform being so flexible and open to different usages. I'd still say the benefits outweighs these complaints ten-fold, but these are the biggest issues we've had with it, and I've raised some of these issues directly with the devtron team, hopefully some of them would be resolved soon.

everything is good but they need more improvement

The product is good but I haven't seen anything around AI. Would love to have features around AI that would help me get cluster info and more details to ease my tasks.