# Install 8.2.0 APM on ECK - "precondition 'apm integration installed'

**URL:** <https://discuss.elastic.co/t/install-8-2-0-apm-on-eck-precondition-apm-integration-installed/306052>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [May 31, 2022, 3:43pm UTC](https://discuss.elastic.co/t/install-8-2-0-apm-on-eck-precondition-apm-integration-installed/306052 "2022-05-31T15:43:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kay\_Khan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kay_khan/32/45028_2.png) [@Kay\_Khan](https://discuss.elastic.co/u/Kay_Khan)\
**Post date:** [May 31, 2022, 3:43pm UTC](https://discuss.elastic.co/t/install-8-2-0-apm-on-eck-precondition-apm-integration-installed/306052/1 "2022-05-31T15:43:24Z")

</div>

I'm deploying an ECK stack on a new kubernetes cluster. I have installed so far and working Elasticsearch, kibana and filebeat.

ps: I don't use "agents or fleet" because i could not get them to work and there was very little support here, my assumption is because it is in technical preview, fine.

But now, I want to install APM however in this newer version (8.2.0) i am getting an error. In version 7 i did not need this `precondition 'apm integration`?

Is the new apm apart of an "agent/integration" now ?

```auto
{"log.level":"error","@timestamp":"2022-05-31T15:39:28.067Z","log.logger":"beater","log.origin":{"file.name":"beater/waitready.go","file.line":62},"message":"precondition 'apm integration installed' failed: error querying Elasticsearch for integration index templates: unexpected HTTP status: 404 Not Found ({\"error\":{\"root_cause\":[{\"type\":\"resource_not_found_exception\",\"reason\":\"index template matching [logs-apm.error] not found\"}],\"type\":\"resource_not_found_exception\",\"reason\":\"index template matching [logs-apm.error] not found\"},\"status\":404}): to remediate, please install the apm integration: https://ela.st/apm-integration-quickstart","service.name":"apm-server","ecs.version":"1.6.0"}

```

**apm.yaml**

```auto
apiVersion: apm.k8s.elastic.co/v1
kind: ApmServer
metadata:
  name: apm-server-prod
  namespace: elastic-system
spec:
  version: 8.2.0
  count: 1
  elasticsearchRef:
    name: "elasticsearch-prod"
  kibanaRef:
    name: "kibana-prod"
  http:
    service:
      spec:
        type: NodePort
  config:
    apm-server:
      auth:
        anonymous:
          rate_limit:
            event_limit: 300
            ip_limit: 1000
          allow_service: ["admin-dashboard"]
      rum: 
        enabled: true
        allow_origins: ["*"]

```

How do i update my kibana configuration to include this apm integration? ( i dont want to manually do anything via the UI)

**kibana.yaml**

```auto
apiVersion: kibana.k8s.elastic.co/v1
kind: Kibana
metadata:
  name: kibana-prod
  namespace: elastic-system
spec:
  version: 8.2.0
  count: 1
  elasticsearchRef:
    name: elasticsearch-prod
  http:
    service:
      spec:
        type: NodePort
  podTemplate:
    spec:
      containers:
      - name: kibana
        resources:
          limits:
            memory: 2Gi
            cpu: 1
      nodeSelector:
        geeiq/node-type: ops

```

---

<div class="post-metadata">

**Author:** ![BenB196](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benb196/32/83401_2.png) [@BenB196](https://discuss.elastic.co/u/BenB196)\
**Post date:** [May 31, 2022, 5:09pm UTC](https://discuss.elastic.co/t/install-8-2-0-apm-on-eck-precondition-apm-integration-installed/306052/2 "2022-05-31T17:09:04Z")

</div>

It isn't very clear in the base install docs of APM Server, but you can find the way to do this via the upgrade docs here: [Upgrade a self-installation of APM Server standalone to 8.2.2 | APM User Guide [8.2] | Elastic](https://www.elastic.co/guide/en/apm/guide/current/upgrade-8.0-self-standalone.html).

See Step 2, and the Warning on Step 3, which explains the error you're seeing.

---

<div class="post-metadata">

**Author:** ![Kay\_Khan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kay_khan/32/45028_2.png) [@Kay\_Khan](https://discuss.elastic.co/u/Kay_Khan)\
**Post date:** [May 31, 2022, 5:12pm UTC](https://discuss.elastic.co/t/install-8-2-0-apm-on-eck-precondition-apm-integration-installed/306052/3 "2022-05-31T17:12:54Z")

</div>

Nice, i didint see that but it forces me to use the UI to do this which i don't want to do

---

<div class="post-metadata">

**Author:** ![Kay\_Khan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kay_khan/32/45028_2.png) [@Kay\_Khan](https://discuss.elastic.co/u/Kay_Khan)\
**Post date:** [May 31, 2022, 5:14pm UTC](https://discuss.elastic.co/t/install-8-2-0-apm-on-eck-precondition-apm-integration-installed/306052/4 "2022-05-31T17:14:28Z")

</div>

I found out how to do it programatically

```auto
spec:  
  config:
    xpack.fleet.packages:
      - name: apm
        version: latest

```

Its very confusing change, i don't use fleet or elastic agents at all because they are in technical preview for ECK and difficult to make changes pragmatically. But seems like i am forced to reference fleet with apm

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 28, 2022, 5:14pm UTC](https://discuss.elastic.co/t/install-8-2-0-apm-on-eck-precondition-apm-integration-installed/306052/5 "2022-06-28T17:14:53Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.