Developers docs for setting up a development environment for working with Helm

Creating this issue here while the decision is made on https://gitlab.com/charts/charts.gitlab.io/issues/15#note_35923539

To make sure that everyone can contribute to the new Helm chart projects that is a part of Build team OKR's, we should first create documentation on how to setup your development environment. For example, by using minikube.

Things to consider for directions:

• should be cross platform
• they should also contain pointers on debugging
• points about cleanup of the cluster to leave a clean state for the next run
• ?? something else

/cc @gitlab-build-team

changed title from Developers docs for setting up an environment for working with Helm to Developers docs for setting up a development environment for working with Helm

@WarheadsSE Can you take this issue as the next task? By the time you start on the issue, @joshlambert and I will have a decision on where they should be.

assigned to @WarheadsSE

@joshlambert where is the documentation of where this should end up?

From looking through available options, minikube seems the most community supported method.

I also found this post that expounds on workflows with minikube

@WarheadsSE can you create them here: https://gitlab.com/charts/helm.gitlab.io

I agree, minikube is the best way to get started locally. We use it for the GDK already. It doesn't support everything, so we may find that we have to make the jump into a "real" k8s platform, but lets try this first.

I agree. We'll start with Minikube, but GKE is the likely next step.

mentioned in merge request charts/helm.gitlab.io!1 (merged)

I believe we should be able to call this issue closed.

closed

closed