Using more than one Helm repositories for profiles for installation

[saeedfazal]

Currently only one HelmRepository object weaveworks-chartscan be defined pointing to a single helm chart repository for profile installation. However, as a user I want to configure multiple helm repositories to be used and available for profile installation during CAPI cluster creation.

User story:

• I want to be able to create a cluster and install cert-manager from the cert-manager helmrepostitory and pod-info from the pod-info helmrespository onto my new cluster.

[foot]

User story:

• Use a WW provided repo for policy-agent etc
• Use own repo for own charts

At the moment can only have a single profile-repo (helmrepo).

[foot]

The helmrepo caching system might already support caching multiple repos etc.

There are places in EE at least where we assume a single repo. Places to consider:

• capitemplate.annos might need { name, version, REPO } now
• GET profiles(template) should look for multiple repos somehow rather than just one named weaveworks-charts

[foot]

Technically we can support multiple helm repos now.. it doesn't work in the UI really, from gitops create template it would though

apiVersion: templates.weave.works/v1alpha2
kind: GitOpsTemplate
metadata:
  name: multi-profile
  namespace: default
  annotations:
    templates.weave.works/profiles-enabled: "false"
    templates.weave.works/delimiters: "${{,}}"
spec:
  renderType: templating
  params:
    - name: CLUSTER_NAME
      required: true
      description: This is used for the cluster naming.
  charts:
    items:
      - chart: cert-manager
        targetNamespace: cert-manager
        version: 0.0.8
        template:
          content:
            metadata:
              namespace: ${{ .params.NAMESPACE }}
            spec:
              chart:
                spec:
                  sourceRef:
                    name: bitnami
                    namespace: ${{ .params.NAMESPACE }}
      - chart: weave-policy-agent
        targetNamespace: policy-agent
        template:
          content:
            metadata:
              namespace: ${{ .params.NAMESPACE }}
            spec:
              chart:
                spec:
                  sourceRef:
                    name: profiles-catalog
                    namespace: ${{ .params.NAMESPACE }}
  resourcetemplates:
    - path: "${{ .params.NAMESPACE }}/helmrepos/bitnami.yaml"
      content:
        - apiVersion: source.toolkit.fluxcd.io/v1beta1
          kind: HelmRepository
          metadata:
            name: bitnami
            namespace: ${{ .params.NAMESPACE }}
          spec:
            url: https://charts.bitnami.com/bitnami
    - path: "${{ .params.NAMESPACE }}/helmrepos/profiles-catalog.yaml"
      content:
        - apiVersion: source.toolkit.fluxcd.io/v1beta1
          kind: HelmRepository
          metadata:
            name: profiles-catalog
            namespace: ${{ .params.NAMESPACE }}
          spec:
            url: https://charts.bitnami.com/bitnami

[bigkevmcd]

This is in-progress.

[foot]

cc @LappleApple we underestimated this one and are putting it on pause for now.