# APM not being deployed as a NodePort

**URL:** <https://discuss.elastic.co/t/apm-not-being-deployed-as-a-nodeport/370374>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [November 12, 2024, 8:19am UTC](https://discuss.elastic.co/t/apm-not-being-deployed-as-a-nodeport/370374 "2024-11-12T08:19:18Z")\
**Posts on this page:** 2\
**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:** [November 12, 2024, 8:19am UTC](https://discuss.elastic.co/t/apm-not-being-deployed-as-a-nodeport/370374/1 "2024-11-12T08:19:18Z")

</div>

We have an ECK cluster running on version 2.14 and we are deploying the APM server. Despite setting `http.service.spec.type: NodePort` the APM server is spawned as a ClusterIP.

```auto
    count: 1
    version: 8.15.2
    fullnameOverride: ${local.apm_server_name}
    spec:
      elasticsearchRef:
        name: ${data.terraform_remote_state.eck_elasticsearch.outputs.elasticsearch_name}
      kibanaRef: 
        name: ${data.terraform_remote_state.eck_kibana.outputs.kibana_name}
      http:
        service:
          spec:
            type: NodePort

```

We use a similiar config for Kibana and Fleet and they are correctly deployed as a NodePort.

This is on a fresh Kubernetes cluster EKS 1.31

---

<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:** [November 13, 2024, 8:27am UTC](https://discuss.elastic.co/t/apm-not-being-deployed-as-a-nodeport/370374/2 "2024-11-13T08:27:52Z")

</div>

I resolved this issue

There is a difference in defining values in the eck-apm-server helm chart compared to all other eck-\* charts.

> **[eck-kibana 0.13.0 · elastic/elastic](https://artifacthub.io/packages/helm/elastic/eck-kibana)**
>
> Kibana managed by the ECK operator

> **[eck-apm-server 0.13.0 · elastic/elastic](https://artifacthub.io/packages/helm/elastic/eck-apm-server)**
>
> Elastic APM Server managed by the ECK operator

In kibana/fleet/elasticsearch/elastic-agents there is a spec object and the apm-server is the only one that does not conform to this convention.