用eck-operator将APM服务器添加到掌舵中

发布于 2025-01-17 15:30:35 字数 2102 浏览 4 评论 0原文

我们有一个现有的 helm 图表,我们用它来执行 helm install eck Operator docker.elastic.co/eck/eck-operator:2.0.0 然后我们有图表,其中有 Elasticsearch、带有角色和 Fluentd 依赖项的 kibana yaml 文件,结构看起来就是这样 输入图片此处描述

现在我添加 apm-server yaml 文件并希望与其他服务一起部署,但它没有部署

apm-server.yaml

apiVersion: apm.k8s.elastic.co/v1
kind: ApmServer
metadata:
  name: {{ .Release.Name }}
  namespace: {{ .Release.Namespace }}
spec:
  type: ApmServer
  version: {{ .Values.elasticStackVersion }}
  count: 1
  elasticsearchRef:
    name: {{ .Release.Name }}
    #name: "es-cluster"
  kibanaRef:
    name: {{ .Release.Name }}
    #name: "kibana"
  podTemplate:
    spec:
      containers:
        - name: {{ .Release.Name }}
        #- name: apm-server
          resources:
            limits:
              memory: 1Gi
              cpu: 1

values.yaml 文件

elasticStackVersion: 8.0.0

elasticsearch:
  image: euaappcorecr.azurecr.io/elasticsearch
  replicaCount: 2
  storageClassName: default
  service:
    type: ClusterIP

kibana:
  image: euaappcorecr.azurecr.io/kibana
  service:
    type: LoadBalancer
    annotations:
      service.beta.kubernetes.io/azure-load-balancer-internal: "true"
      service.beta.kubernetes.io/azure-load-balancer-internal-subnet: "Lb_External_IP"

metricbeat:
  enabled: false
  image: euaappinfracr.azurecr.io/metricbeat


ApmServer:
  image:
    repository: euaappcorecr.azurecr.io/apm-server
    tag: 8.0.0
    pullPolicy: IfNotPresent
  service:
    type: ClusterIP

fluentd:
  image:
    registry: euaappinfracr.azurecr.io
    repository: fluentd
    tag: bitnami-1.11.5
  forwarder:
    enabled: false
  aggregator:
    enabled: true
    configMap: elasticsearch-output
    persistence:
      enabled: true    
      storageClass: default
      size: 5Gi

cmd: helm install efk-dev 。 -n efk-dev --create-namespace --dependency-update -f value.yaml

We have an existing helm chart where we use to do helm install eck operator docker.elastic.co/eck/eck-operator:2.0.0
Then we have chart in which we have elasticsearch, kibana yaml file with roles and fluentd dependencies, Structure looks lie this
enter image description here

Now i'm adding apm-server yaml file and hoping to get deployed along with other services, but its is not getting deployed.

apm-server.yaml

apiVersion: apm.k8s.elastic.co/v1
kind: ApmServer
metadata:
  name: {{ .Release.Name }}
  namespace: {{ .Release.Namespace }}
spec:
  type: ApmServer
  version: {{ .Values.elasticStackVersion }}
  count: 1
  elasticsearchRef:
    name: {{ .Release.Name }}
    #name: "es-cluster"
  kibanaRef:
    name: {{ .Release.Name }}
    #name: "kibana"
  podTemplate:
    spec:
      containers:
        - name: {{ .Release.Name }}
        #- name: apm-server
          resources:
            limits:
              memory: 1Gi
              cpu: 1

values.yaml file

elasticStackVersion: 8.0.0

elasticsearch:
  image: euaappcorecr.azurecr.io/elasticsearch
  replicaCount: 2
  storageClassName: default
  service:
    type: ClusterIP

kibana:
  image: euaappcorecr.azurecr.io/kibana
  service:
    type: LoadBalancer
    annotations:
      service.beta.kubernetes.io/azure-load-balancer-internal: "true"
      service.beta.kubernetes.io/azure-load-balancer-internal-subnet: "Lb_External_IP"

metricbeat:
  enabled: false
  image: euaappinfracr.azurecr.io/metricbeat


ApmServer:
  image:
    repository: euaappcorecr.azurecr.io/apm-server
    tag: 8.0.0
    pullPolicy: IfNotPresent
  service:
    type: ClusterIP

fluentd:
  image:
    registry: euaappinfracr.azurecr.io
    repository: fluentd
    tag: bitnami-1.11.5
  forwarder:
    enabled: false
  aggregator:
    enabled: true
    configMap: elasticsearch-output
    persistence:
      enabled: true    
      storageClass: default
      size: 5Gi

cmd: helm install efk-dev . -n efk-dev --create-namespace --dependency-update -f values.yaml

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文