Iasluhar

Here is the Part - 2:

https://devtron.ai/blog/aws-cost-optimization-parameters-and...

Hey Everyone, as Kubernetes is ready to release its version 1.22, Developers and DevOps Engineers need to upgrade Kubernetes Objects before upgrading Kubernetes. It's a tedious task to know whether the current ApiVersion of the Object is Removed, Deprecated or Unchanged. We thought why not build a tool, Silver-Surfer, that would not only validate against the given Kubernetes version but also provides a Migration Path to a newer ApiVersion. It shows exact errors which need to be resolved for migration to newer ApiVersion as well as specification errors with respect to the provided ApiVersion in case it is not removed.

https://github.com/devtron-labs/silver-surfer

I know that there are other tools that provide similar functionality but they seemed Inadequate Kubeval(link of Kubeval) - Well known, It only validates against the given Kubernetes Version but doesn’t provide a migration path Kubent(Link of Kubent) - Only provides Info about removed and deprecated api but no schema validation Kubepug(Link of KubePug) - Only checks whether the existing objects have any Deprecated ApiVersions

Silver-Surfer uses openapi spec provided by the Kubernetes with releases, for eg. in case of target kubernetes version 1.22 openapi spec for 1.22, to validate the Kubernetes objects for depreciation or non-conformity with openapi spec. This allows it to validate against any kubernetes version as soon as its specs are released on the github kubernetes project.

It's a side project we took up as these issues were a hassle upgrading one of our Platforms, Devtron. Would love to know what you think of this, any suggestions and Contributions are welcome :)

Devtron is an opensource Experience of a SaaS product with the tools of your choice without the lock in of a SaaS product. It manages and Operationalizes applications on Kubernetes.

https://github.com/devtron-labs/devtron

It integrates with the existing open-source systems like argocd, Argo workflow, Clair, hibernator, grafana, Prometheus, envoy, and many others and add capabilities on top of them to enable clean self serve UI for developers and DevOps We got a lot of questions on how to use it, what are the use cases, how to get started and others . That's the reason we are conducting a LiveStream. One of our maintainers Prashant would be joining Saiyam Pathak, Director at Civo and YouTuber, to have a chat and a demo of Devtron.

Devtron is an Opensource tool that provides End-to-End Kubernetes Software Delivery Workflow. We recently added support for the installation of Devtron on MiniKube as well.

Blog: https://hackernoon.com/how-to-install-devteron-over-minikube...

It would be really great if you could give your feedback and suggestions regarding Devtron and the new feature, to make it better and provide the community an overall better experience.

Hey all, We started working on our opensource project around two years ago. The project is about the software delivery workflow for Kubernetes. We needed a Dashboard functionality for the users to show various metrics for CI/CD processes like deployment failure, Lead time, Deployment Size, and others.

In the blog, we tried to go over the whole process step-by-step and improve it to optimize agile process. From sharing the evolution of the dashboard, the initial failure, and its realization, and then how we evolved our UX to how it is today. We are still on this journey and would love to have your feedback on making it better.

Oh okay, got it. Yea that's true, there should have been plenty of resources and low population. In that case exchanging ideas is indeed difficult.

Yea, people love to correlate and make conclusions without digging deeper. That is definitely a problem

I hope there's more than that. It will be disappointing otherwise.

Yea, but I don't know if MS would go that far. Before that, don't you think they would make it Opensource (highly improbable) but you know a sliver of chance.

Yea, but the article is more towards who has the power to implement these decisions and why is it concentrated towards a small population.

Haha, now we live in a society where there is a pretence that we can become powerful although a negligible percentage make it through.

I think your points are true if we consider the last 2000 years but the article basically points out on why the transformation happened before that time(12000 years ago). If we consider hunters and foragers at that time, the oppression on creativity might not work and in my opinion is more free and real(no monetary benefit). At that time only thing they might have cared is, whether there is enough food for themselves and their families. Sure, there might be differences in physical strengths a little bit, but I don't think that would be such a big offset.