Migrate istio resources to helm #15

New Issue

2023-02-22T09:22:16Z

allanger commented

2023-02-22 09:22:16 +00:00

(Migrated from git.badhouseplants.net)

Possible options that I see now:

Use sub-chart
Use the raw chart https://artifacthub.io/packages/helm/main/raw
Use kustomize

Possible options that I see now: - Use sub-chart - Use the raw chart https://artifacthub.io/packages/helm/main/raw - Use kustomize

allanger commented

2023-03-05 08:32:31 +00:00

(Migrated from git.badhouseplants.net)

I'd start with the "raw" chart.

With helmfile you can add a sub-chart without forking the chart. https://helmfile.readthedocs.io/en/latest/advanced-features/#adding-dependencies-without-forking-the-chart

The idea is to add the "raw" chart as a dependency, and create some common values, that can be used in each release. Example for gitea can be found here: https://git.badhouseplants.net/badhouseplants/k8s-cluster-config/src/branch/main/badhouseplants/values/values.gitea.yaml

But this example can not generate several VSs for one chart, so I think it should be a template with a for loop. Also, service name should be taken from the release, if possible.

Here is a release template example b03661222a/releases.yaml (L38)

AC:

There is an additional field added to release-templated

  gitea: &gitea
    name: gitea
    chart: gitea/gitea
    version: 7.0.2
    inherit: 
      - template: default-env-values
      - template: default-env-secrets
      - template: ext-istio-vs

In the release values it should look like

istio:
  vs:
    - name: gitea-http
      port: 3000
      service: gitea-http

But without hardcoded values, if possible.

After applying, new virtual services should be created

I'd start with the "raw" chart. With `helmfile` you can add a sub-chart without forking the chart. https://helmfile.readthedocs.io/en/latest/advanced-features/#adding-dependencies-without-forking-the-chart The idea is to add the "raw" chart as a dependency, and create some common values, that can be used in each release. Example for gitea can be found here: https://git.badhouseplants.net/badhouseplants/k8s-cluster-config/src/branch/main/badhouseplants/values/values.gitea.yaml But this example can not generate several `VSs` for one chart, so I think it should be a template with a for loop. Also, service name should be taken from the release, if possible. Here is a release template example https://git.badhouseplants.net/badhouseplants/k8s-cluster-config/src/commit/b03661222ace0eb5807b11512a3dfdf7da61fca7/releases.yaml#L38 --- AC: - There is an additional field added to release-templated ```YAML gitea: &gitea name: gitea chart: gitea/gitea version: 7.0.2 inherit: - template: default-env-values - template: default-env-secrets - template: ext-istio-vs ``` - In the release values it should look like ```YAML istio: vs: - name: gitea-http port: 3000 service: gitea-http ``` But without hardcoded values, if possible. - After applying, new virtual services should be created

This repo is archived. You cannot comment on issues.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: badhouseplants/k8s-cluster-config#15