asymmetric

To the point of the issue: I think the way we do it now is that we update the examples once we release a new version. Basically, right now running...

I think we probably don't need to have a `service` key at all, i.e. we can just one level of depth.

@zeenix WDYT? Flattening the type layout will be a breaking change, and you seem to have strong feelings towards backwards compatibilty. Also /cc @krnowak @LiliC

Basically, ```yaml apiVersion: habitat.sh/v1beta1 kind: Habitat metadata: name: example-configured-habitat spec: image: kinvolk/redis-hab count: 1 service-name: db topology: standalone group: redisdb configSecretName: user-toml ```

After thinking about this some more, I think the current structure is fine, and that `configSecretName` is just an outlier that is probably misplaced Basically, the "rationale" IMO is that...

Why a tarball? What's the usecase? (Also, added to the board)

So, IIUC, the fact that the URL returns 404 when accessed directly does not break anything, because helm actually fetches the `index.yaml` file. If so, I guess we can close...

Or rather: * Is the user expectation that they should be able to navigate the charts by following that link? * If so, would we be better served by hosting...

The loop will not be infinite, there's [a limit](https://github.com/habitat-sh/habitat-operator/blob/master/pkg/controller/v1beta2/controller.go#L1470) to how many times an object is requeued.

Oops, here's the [correct link](https://github.com/habitat-sh/habitat-operator/blob/master/pkg/controller/v1beta2/controller.go#L148).