add documentation about a use case using okteto registry to store helm charts

[AdrianPedriza]

We need to add some kind of documentation, probably in the form of a blog post or something similar in the okteto community. This post should include a common use case for working with the okteto registry as a chart store where in a particular repo you have the definition of the charts and in each merge these are packed and stored in the okteto registry. After that, the developers work with in their developments making pull of the last changes of the charts loaded in the okteto registry.

more context:

• https://github.com/okteto/movies-api/tree/oci-chart
• add docs about push helm chart into okteto registry #221 (comment)

[rberrelleza]

done! @AdrianPedriza do you think https://www.okteto.com/docs/cloud/registry/#push-helm-chart-into-the-okteto-registry is enough?

[AdrianPedriza]

@rberrelleza we have the documentation letting the user know that he can also store helm chart in the registry but no detailed documentation explaining one of the use cases involved: deploy my development environment from the charts stored in the registry (which may have followed a different integration flow). @pchico83 do you think we still need this kind of use case documentation or is the current one enough?

[pchico83]

@rberrelleza we have the documentation letting the user know that he can also store helm chart in the registry but no detailed documentation explaining one of the use cases involved: deploy my development environment from the charts stored in the registry (which may have followed a different integration mechanism.). @pchico83 do you think we still need this kind of use case documentation or is the current one enough?

We need it, but it' lower priority than other documentation efforts