Gimlet Stack packages Helm Charts and delivers it with gitops, using the Helm Controller from the Flux V2 project.

A curated stack supports a basic set of flags, but significantly less than the underlying Helm charts.

The task is to come up with a file format that is able to hold together ~25 Helm charts and its exposed flags. Kind of like umbrella Helm charts.

Should the host field be mendetory when configuring nginx?

Reproduce:

1. Add Prometheus und Loki with stack configure
2. Also add Nginx without a host
3. See broken host config in helm-releases/grafana.yaml

Currently the formatting of readmes in thestack configureui is broken. I think it is because of theprose` class does not get generated or purged. Therefore I would use the JIT mode so it is visible in development what comes out at the end (in contrast to the purge mode)

See: https://tailwindcss.com/docs/just-in-time-mode#enabling-jit-mode

prose has no effect as of now:

stack bootstrap command to bootstrap Flux V2 manifests in a local git repo.

Follow the steps of https://github.com/gimlet-io/gimlet-cli/tree/main/commands/gitops, make modifications where needed.

Make decisions on the scaling model: one repo per environment, or one git repo with environments as folders.

kubectl apply -f /home/laszlo/projects/laci/laci-gitops/test/flux/gitops-repo.yaml

should be

kubectl apply -f /home/laszlo/projects/laci/laci-gitops/test/flux/gitops-repo-<<env>>.yaml

---
layout: gimlet-stack
title: Getting Started
lastUpdated: 2021-05-17
image: gimlet-stack.png
tags: [gimlet-stack]
---

# Getting Started

Bootstrap curated Kubernetes stacks!

Logging, metrics, ingress and more - all delivered with gitops.

- You can install logging aggregators, metric collectors, ingress controllers and more on your cluster with a few commands, 
without much knowledge of Helm charts, and their configuration options

- The components are delivered through a plain git repository with self-contained gitops automation

- You will get constant upgrades for the installed components from the stack curators

Read the [concepts](/gimlet-stack/concepts) behind Gimlet Stack or [bootstrap your first stack](/gimlet-stack/bootstrap-your-first-stack).

and technical concepts:

---
layout: gimlet-stack
title: Concepts
lastUpdated: 2021-05-17
image: gimlet-stack.png
tags: [gimlet-stack]
---

# Concepts

Gimlet Stack is a command line tool that you can use to configure curated stacks for Kubernetes clusters.

*Stack makers* (or curators) maintain the stacks, and *end-users* benefit from the curator's hard-earned best practices as they deploy the curated stacks on their clusters.

A stack instance - with its complete configuration - is stored in a git repository and delivered onto a kubernetes cluster via a gitops automation.
Gimlet Stack uses Flux V2 as the gitops controller to sync git changes to the cluster. 

The full overview of the various artifacts and actors of Gimlet Stack:
![Gimlet Stack concepts](/stack-concepts.png)

## End-user workflow

- end-users create a `stack.yaml` file with the full configuration of their stack: enabling the needed components, and configuring them through a series of options
  - end-users can create the `stack.yaml` manually
  - or through the `stack configure` CLI command which opens a browser based UI from the terminal
- users store the `stack.yaml` in git [email protected]:mycompany/gitops-infra-staging.git
- users generate HelmRelease resources and other Kubernetes manifests from the components defined in `stack.yaml` with the `stack generate` CLI command
- users store the generated files in the same git repository as the `stack.yaml` file


- users push the changes to git, and the bootstrapped gitops loop syncs it on the cluster.
- users can bootstrap the gitops loop with the `stack bootstrap` CLI command

## Stacks

Stacks are a set of Helm charts and Kubernetes manifests that are configured to work together seamlessly.

- stacks use the well known community Helm charts 
- stacks expose only a subset of helm chart values to users to limit the decision space
- stacks make it possible to use all chart values if people want the full chart feature set / optionality
- stacks create new chart values that group together multiple flags, and abstract them at a higher level. Eg.: stickySessions, realIP, HA
- stacks don't change the community charts, as upstreaming opinions will be a blocker every time. Instead, stacks wrap/compose the community charts 
- stacks are able to deliver raw yamls to the gitops repo, configmaps, etc


## Next steps

To see Gimlet Stack in action, go and [bootstrap your first stack](/gimlet-stack/bootstrap-your-first-stack).