Blog: Simplifying Kubernetes Resource Management with AWS Kro #49133
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Hey folks. I've wrote a small article on the recently open-sourced Kro project by AWS. I think it's a great way to simplify many deployments, and sits somewhere in-between helm and a full-blown operator.
This article presents the basics on how Kro ResourceGroups are designed and how to use them using a real-world example of Simplyblock.
Would love to hear your feedback. Specifically on the last section. Not sure if I'm ok to say that there were good and bad things about the stewardship of open-source projects with AWS in the past or if I should better remove it for objectivity.
Attention: In the blog post, I utilize simplyblock as an example of how Kro could be used and why it would be beneficial. However, due to being an employee of simplyblock, I want to bring this up here as a potential conflict of interest. I don't assume this blog post to be a product pitch, but still.