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:
Development of
Docker files
Helm Charts
Fresh install use case
Upgrade use case
Evolution of values files from release to release
Automation of builds on CI
Build Docker images
Build Helm packages
Automation of testing with built Docker images using the helm chart
testing fresh installs
testing upgrade
implement backup before upgrade strategy
testing rollbacks
implement restore after rollback
Implementation of tag and helm chart versioning pre-test and for release
Build and prepare release artifacts for Docker images and Helm package
Supporting fresh installs
Documentation of the values files and process
Supporting upgrades
Documentation of the values files evolution for customers previous version of values files and process of backup, upgrade
Dealing with upgrade failures implement recovery using backup/restore and helm rollbacks
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.
