訪問依賴項的helm背景關系

我們正在使用這個圖表：

apiVersion: v2
appVersion: 1.0
version: 0.0.1
description: Helm chart for setting up Kafka platform (Kafka, Zookeeper, Kafka Rest, Kafka Schema Registry, Kafka Connect, KSQL Server)
name: kafka-platform

dependencies:
  - name: cp-helm-charts
    version: 0.6.0
    repository: "https://confluentinc.github.io/cp-helm-charts"

我們需要創建公共圖表中不存在的新本地模板，并且這個新模板應該訪問公共圖表中定義的內置變數。例如，.Chart.Name

apiVersion: v1
appVersion: "1.0"
description: A Helm chart for Confluent Kafka on Kubernetes
name: cp-kafka
version: 0.1.0

我們如何從名為模板或模板的本地 .tpl 訪問“cp-kafka”？我現在設法訪問的只是“<.Chart.Name> 處的“型別錯誤：無法評估 int 型別的欄位圖表”或本地圖表“kafka-platform”的值。

我已經搜索過這個問題/答案，但是雖然我看到了相似的東西，但我沒有找到一個完全適合或回答這個確切問題的東西。

uj5u.com熱心網友回復：

您可以使用子圖表地圖。

{{ $sub := index .Subcharts "cp-kafka" }}

這將為您提供所有內置變數，甚至.Values來自值檔案。

例如，我創建一個圖表和一個子圖表：

helm create foo
helm create foo/charts/bar
rm -rf foo/templates/*
rm -rf foo/charts/bar/templates/*

在 bar 值中，我把這個：

some:
  values: from
  this: subchart

在 foo 模板中，我放置了這個 configmap：

kind: ConfigMap
apiVersion: v1
metadata:
  name: example
data:
  bar-chart: |
    {{- .Subcharts.bar | toYaml | nindent 4 }}

現在，當我渲染圖表時，helm template foo我得到以下輸出：

---
# Source: foo/templates/cm.yaml
kind: ConfigMap
apiVersion: v1
metadata:
  name: example
data:
  bar-chart: |
    Capabilities:
      APIVersions:
      - v1
      - admissionregistration.k8s.io/v1
      - admissionregistration.k8s.io/v1beta1
      - internal.apiserver.k8s.io/v1alpha1
      - apps/v1
      - apps/v1beta1
      - apps/v1beta2
      - authentication.k8s.io/v1
      - authentication.k8s.io/v1beta1
      - authorization.k8s.io/v1
      - authorization.k8s.io/v1beta1
      - autoscaling/v1
      - autoscaling/v2
      - autoscaling/v2beta1
      - autoscaling/v2beta2
      - batch/v1
      - batch/v1beta1
      - certificates.k8s.io/v1
      - certificates.k8s.io/v1beta1
      - coordination.k8s.io/v1beta1
      - coordination.k8s.io/v1
      - discovery.k8s.io/v1
      - discovery.k8s.io/v1beta1
      - events.k8s.io/v1
      - events.k8s.io/v1beta1
      - extensions/v1beta1
      - flowcontrol.apiserver.k8s.io/v1alpha1
      - flowcontrol.apiserver.k8s.io/v1beta1
      - flowcontrol.apiserver.k8s.io/v1beta2
      - networking.k8s.io/v1
      - networking.k8s.io/v1beta1
      - node.k8s.io/v1
      - node.k8s.io/v1alpha1
      - node.k8s.io/v1beta1
      - policy/v1
      - policy/v1beta1
      - rbac.authorization.k8s.io/v1
      - rbac.authorization.k8s.io/v1beta1
      - rbac.authorization.k8s.io/v1alpha1
      - scheduling.k8s.io/v1alpha1
      - scheduling.k8s.io/v1beta1
      - scheduling.k8s.io/v1
      - storage.k8s.io/v1beta1
      - storage.k8s.io/v1
      - storage.k8s.io/v1alpha1
      - apiextensions.k8s.io/v1beta1
      - apiextensions.k8s.io/v1
      HelmVersion:
        git_commit: 6e3701edea09e5d55a8ca2aae03a68917630e91b
        git_tree_state: clean
        go_version: go1.17.5
        version: v3.8.2
      KubeVersion:
        Major: "1"
        Minor: "23"
        Version: v1.23.0
    Chart:
      IsRoot: false
      apiVersion: v2
      appVersion: 1.16.0
      description: A Helm chart for Kubernetes
      name: bar
      type: application
      version: 0.1.0
    Files:
      .helmignore: IyBQYXR0ZXJucyB0byBpZ25vcmUgd2hlbiBidWlsZGluZyBwYWNrYWdlcy4KIyBUaGlzIHN1cHBvcnRzIHNoZWxsIGdsb2IgbWF0Y2hpbmcsIHJlbGF0aXZlIHBhdGggbWF0Y2hpbmcsIGFuZAojIG5lZ2F0aW9uIChwcmVmaXhlZCB3aXRoICEpLiBPbmx5IG9uZSBwYXR0ZXJuIHBlciBsaW5lLgouRFNfU3RvcmUKIyBDb21tb24gVkNTIGRpcnMKLmdpdC8KLmdpdGlnbm9yZQouYnpyLwouYnpyaWdub3JlCi5oZy8KLmhnaWdub3JlCi5zdm4vCiMgQ29tbW9uIGJhY2t1cCBmaWxlcwoqLnN3cAoqLmJhawoqLnRtcAoqLm9yaWcKKn4KIyBWYXJpb3VzIElERXMKLnByb2plY3QKLmlkZWEvCioudG1wcm9qCi52c2NvZGUvCg==
    Release:
      IsInstall: true
      IsUpgrade: false
      Name: release-name
      Namespace: default
      Revision: 1
      Service: Helm
    Subcharts: {}
    Values:
      global: {}
      some:
        this: subchart
        values: from

標籤：Kubernetes kubernetes-helm

上一篇：nginx映像在kubectl部署和pod中的行為不同

下一篇：索引固定完成計數作業，多個具有相同索引的pod