How are people estimating efforts for developing and maintaining Helm chart based product releases?
Thanks for your comprehensive response.
Loritsch, Berin <bloritsch@...>
toggle quoted message Show quoted text
Helm definitely has some wrinkles, and I've run into a few. So I would recommend separating your tasking. For example:
You do need to test those scenarios, but they shouldn't be separate tasking.
Regarding CI/CD, I recommend you look into the various Continuous Deployment tools for Kubernetes clusters. For example, FluxCD and/or ArgoCD both work with Helm and manage your configuration and deployment for your environment(s). Your Continuous Integration platform of choice builds the different packages (containers and helm charts) and deploys them to your local repository (like Sonatype Nexus or JFrog Artifactory). Your CD tool of choice pulls those new packages from that repository and updates your deployments as necessary.
It's a lot of moving parts, but each part does have a specific purpose.
On Wed, May 5, 2021 at 10:41 PM Sandip Chitale <sandipchitale@...> wrote:
7921 Jones Branch Drive
Office (703) 735-6281
Mobile (571) 215-7708
This is a somewhat open ended question but I am looking for some real world, practical knowledge/experience about effort estimation for developing and maintaining Helm chart based products.
Helm3 is supposed to make deployment of applications to Kubernetes platform easy. The helm install/upgrade/rollback single commands to do the deployments on the surface make it sound easy. But this is slightly deceptive though. The actual process involves:
I am looking for information like what effort estimation/story points estimation strategies people are using.
Practically, how many people are working in your teams on the full development lifecycle discussed above. Of course this may vary from team to team and product to product. All aspects above may or may not apply to your projects.
I think how to estimate java, dotnet, frontend projects is relatively well as we have been developing those for some time.
Do you have any insights to share?
|1 - 3 of 3|