# Kubernetes Monitoring

Bindplane supports managing Kubernetes agents allowing you to streamline the observability of your cluster. Before following this guide, be sure to familiarize yourself with the [Kubernetes Install, Upgrade, and Uninstall Agents](https://app.gitbook.com/s/gmiOMzBfoNFwmKJFHMcJ/deployment/kubernetes/collector/install) documentation.

### Objective

Monitoring a Kubernetes cluster involves collecting metrics and logs from various components that makeup the cluster.

#### Metrics

**Kubelet**

The [Kubelet API](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/) is hosted on each node within the cluster. It can be used to gather node, pod, container, and volume metrics. Each Kubelet's scope is limited to the node it is running on.

The Kubelet API is useful for tracking pod and container performance metrics, such as CPU or memory utilization.

**API Server**

The [Kubernetes API Server](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/) is hosted within the cluster as a Deployment. It can be used to gather higher-level cluster metrics, such as Deployment or Pod phase.

#### Logs

**Container Logs**

Kubernetes container logs are written to the node's filesystem. Each Kubernetes node is responsible for hosting these logs. Generally, the logs are written to `/var/log/pods` and are symlinked in `/var/log/containers`.

Each log file has the following format:

```
<pod name>_<namespace name> _<container name>-<container id>.log
```

The Bindplane Collector will extract metadata from the log file name following OpenTelemetry's [Semantic Conventions](https://opentelemetry.io/docs/specs/semconv/resource/k8s/).

**Cluster Events**

The Kubernetes API server can be used to retrieve [Kubernetes Events](https://kubernetes.io/docs/reference/kubernetes-api/cluster-resources/event-v1/) in the form of logs.

Kubernetes Events are useful for observing issues such as pod crash loop event.

#### Tracing

Kubernetes does not emit traces, however, applications instrumented to emit OpenTelemetry traces are supported. See the [OpenTelemetry](#opentelemetry) section for details.

#### OpenTelemetry

If your applications are instrumented with OpenTelemetry, they can be configured to forward metrics, traces, and logs to the Bindplane Collectors.

### Implementation

This guide will describe how to configure three configurations:

* Kubernetes Node
* Kubernetes Cluster
* Kubernetes Gateway

The Bindplane Node and Cluster agents will forward their telemetry to the Bindplane Gateway\
agent(s) using a [clusterIP service](https://kubernetes.io/docs/concepts/services-networking/service/).

#### Prerequisites

You should have the following in place before moving forward with Bindplane Kubernetes Agent deployment.

* Access to your Kubernetes cluster
* Access to your Bindplane server

If you do not have Bindplane installed, you can follow one of these two guides for deploying Bindplane to a Linux server or Kubernetes.

* [Install Bindplane Server](https://app.gitbook.com/s/gmiOMzBfoNFwmKJFHMcJ/deployment/virtual-machine/bindplane/install-bindplane-server)
* [Install Bindplane Server on Kubernetes](https://app.gitbook.com/s/gmiOMzBfoNFwmKJFHMcJ/deployment/kubernetes/server/installation)

#### Create Configurations

Before agents can be deployed to the cluster, configurations must be created.

**Node Configuration**

On the Configurations page, choose "Create Configuration". Create a Kubernetes Node configuration. The node configuration will be deployed as a DaemonSet. The DaemonSet will allow the collection of container logs and Kubelet metrics from each node.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/dbcsCJn2bFvaucAwFWqy/how-to-guides-kubernetes-kubernetes-monitoring-image-1.png" alt="Bindplane docs - Kubernetes Monitoring - image 1"><figcaption></figcaption></figure>

Choose next to view the list of available sources.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/JYI34yqSlIC674xWfDmD/how-to-guides-kubernetes-kubernetes-monitoring-image-2.png" alt="Bindplane docs - Kubernetes Monitoring - image 2"><figcaption></figcaption></figure>

Select the Container source and configure it with a cluster name. You can use placeholder value if you intend to detect the cluster name using the [resource detection processor](https://app.gitbook.com/s/gmiOMzBfoNFwmKJFHMcJ/integrations/processors/resource-detection). This processor can be configured during the [gateway configuration](https://docs.bindplane.com/how-to-guides/cloud-and-platform-integrations/kubernetes/kubernetes-monitoring) setup.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/ohHf4J6jdVW8wpVTSAWK/how-to-guides-kubernetes-kubernetes-monitoring-image-3.png" alt="Bindplane docs - Kubernetes Monitoring - image 3"><figcaption></figcaption></figure>

Select the Kubelet source and configure it with a cluster name. You can use placeholder value if you intend to detect the cluster name using the [resource detection processor](https://app.gitbook.com/s/gmiOMzBfoNFwmKJFHMcJ/integrations/processors/resource-detection). This processor can be configured during the [gateway configuration](https://docs.bindplane.com/how-to-guides/cloud-and-platform-integrations/kubernetes/kubernetes-monitoring) setup.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/p9HzqRBfB7Bvbr5jADEg/how-to-guides-kubernetes-kubernetes-monitoring-image-4.png" alt="Bindplane docs - Kubernetes Monitoring - image 4"><figcaption></figcaption></figure>

Optionally, select the OpenTelemetry source. The DaemonSet can receive metrics, logs, and traces from\
applications in your cluster. If you would prefer to have your Gateway Agent handle receiving OpenTelemetry, you can skip this step.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/Bg2shfoLvtEgPuVwaYVP/how-to-guides-kubernetes-kubernetes-monitoring-image-5.png" alt="Bindplane docs - Kubernetes Monitoring - image 5"><figcaption></figcaption></figure>

At this point, you should have both Kubernetes sources and the OpenTelemetry (optional) source.\
Choose next to move to the destination configuration page.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/iwfEPk9pQHUXBFYdFIeS/how-to-guides-kubernetes-kubernetes-monitoring-image-6.png" alt="Bindplane docs - Kubernetes Monitoring - image 6"><figcaption></figcaption></figure>

Search for "OpenTelemetry" and select the "OpenTelemetry (OTLP)" destination.

Configure the `hostname` field with the following value:

```
bindplane-gateway-agent.bindplane-agent.svc.cluster.local
```

Leave all other options set to their default values.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/QzZrIwDWy3ctyhSZVrU2/how-to-guides-kubernetes-kubernetes-monitoring-image-7.png" alt="Bindplane docs - Kubernetes Monitoring - image 7"><figcaption></figcaption></figure>

Once you have configured the destination, choose "Save".

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/YFgkpe1JINlcBGMrzRqI/how-to-guides-kubernetes-kubernetes-monitoring-image-8.png" alt="Bindplane docs - Kubernetes Monitoring - image 8"><figcaption></figcaption></figure>

You will be presented with the new pipeline.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/bHQQQUJZZtBnXB25gzxa/how-to-guides-kubernetes-kubernetes-monitoring-image-9.png" alt="Bindplane docs - Kubernetes Monitoring - image 9"><figcaption></figcaption></figure>

**Cluster Configuration**

On the Configurations page, choose "Create Configuration". Create a Kubernetes Cluster configuration.\
The cluster configuration will be deployed as a Deployment with a single pod. The Deployment will\
allow the collection of cluster metrics and events (logs) from the Kubernetes API server.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/46JkFmxKyQhxfYjaigda/how-to-guides-kubernetes-kubernetes-monitoring-image-10.png" alt="Bindplane docs - Kubernetes Monitoring - image 10"><figcaption></figcaption></figure>

Choose next to view the list of available sources.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/pqJqKyBjY03em3Lx1lbR/how-to-guides-kubernetes-kubernetes-monitoring-image-11.png" alt="Bindplane docs - Kubernetes Monitoring - image 11"><figcaption></figcaption></figure>

Select the Kubernetes Cluster source and configure it with a cluster name. You can use placeholder value if you intend to detect the cluster name using the [resource detection processor](https://app.gitbook.com/s/gmiOMzBfoNFwmKJFHMcJ/integrations/processors/resource-detection). This processor can be configured during the [gateway configuration](https://docs.bindplane.com/how-to-guides/cloud-and-platform-integrations/kubernetes/kubernetes-monitoring) setup.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/ZBx9058UOPeZmv7tWdID/how-to-guides-kubernetes-kubernetes-monitoring-image-12.png" alt="Bindplane docs - Kubernetes Monitoring - image 12"><figcaption></figcaption></figure>

Select the Kubernetes Events source and configure it with a cluster name. You can use placeholder value if you intend to detect the cluster name using the [resource detection processor](https://app.gitbook.com/s/gmiOMzBfoNFwmKJFHMcJ/integrations/processors/resource-detection). This processor can be configured during the [gateway configuration](https://docs.bindplane.com/how-to-guides/cloud-and-platform-integrations/kubernetes/kubernetes-monitoring) setup.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/Inz2tXjVGUGtZloM27ka/how-to-guides-kubernetes-kubernetes-monitoring-image-13.png" alt="Bindplane docs - Kubernetes Monitoring - image 13"><figcaption></figcaption></figure>

At this point, you should have both Kubernetes sources. Choose "next" to move to the destination\
configuration page.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/st1FuAIrYFWMxTTFGMPC/how-to-guides-kubernetes-kubernetes-monitoring-image-14.png" alt="Bindplane docs - Kubernetes Monitoring - image 14"><figcaption></figcaption></figure>

Select the same destination that you created for the node configuration and choose "Save".

Once the configuration is saved, you will be presented with the new pipeline.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/0Nk6K49ohawaj7RoKqcs/how-to-guides-kubernetes-kubernetes-monitoring-image-15.png" alt="Bindplane docs - Kubernetes Monitoring - image 15"><figcaption></figcaption></figure>

**Gateway Configuration**

On the Configurations page, choose "Create Configuration". Create a Kubernetes Gateway configuration. The gateway configuration will be deployed as a StatefulSet.

{% hint style="info" %}
**NOTE**

Deployment with HPA will be supported in the future, as an alternative to StatefulSet.
{% endhint %}

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/Neo0i70aajvC4HXRYyyZ/how-to-guides-kubernetes-kubernetes-monitoring-image-16.png" alt="Bindplane docs - Kubernetes Monitoring - image 16"><figcaption></figcaption></figure>

Choose next to view the list of available sources. Select the OpenTelemetry (OTLP) source. The default\
values will match the values used by the previously created OpenTelemetry destination. This will allow\
the Gateway Agent to receive telemetry from the other agents.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/fUQoPHnipP7oXJLFjb30/how-to-guides-kubernetes-kubernetes-monitoring-image-17.png" alt="Bindplane docs - Kubernetes Monitoring - image 17"><figcaption></figcaption></figure>

After saving the source, choose next to move to the destination configuration page.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/FQ2v4ezrCibyfjNGIyMu/how-to-guides-kubernetes-kubernetes-monitoring-image-18.png" alt="Bindplane docs - Kubernetes Monitoring - image 18"><figcaption></figcaption></figure>

In this example, I am going to use the Google Cloud destination. Feel free to choose the destination\
that best fits your environment. If you do not have a destination at this time, you can use the `custom`\
destination and configure the logging exporter. This exporter will act as a "no-op", and allow you\
to test the configuration without shipping telemetry to a real destination.

Example Google Cloud destination:

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/WnEn51mgtT6SjwrUWizR/how-to-guides-kubernetes-kubernetes-monitoring-image-19.png" alt="Bindplane docs - Kubernetes Monitoring - image 19"><figcaption></figcaption></figure>

If you would like to use the custom destination, enable all three telemetry options and include the\
following for the configuration block:

```yaml
logging:
```

Example Logging destination:

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/VJ1MqsVsPQQX0h5iYxKm/how-to-guides-kubernetes-kubernetes-monitoring-image-20.png" alt="Bindplane docs - Kubernetes Monitoring - image 20"><figcaption></figcaption></figure>

Once you have configured the destination, choose "Save".

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/XLZAqTs9QW1SOUWKwNru/how-to-guides-kubernetes-kubernetes-monitoring-image-21.png" alt="Bindplane docs - Kubernetes Monitoring - image 21"><figcaption></figcaption></figure>

You will be presented with the new pipeline.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/Xh0GCYNp3S50N6pPanHJ/integrations-processors-resource-detection-image-1.png" alt="Bindplane docs - Kubernetes Monitoring - image 22"><figcaption></figcaption></figure>

If you would like to detect the Kubernetes Cluster name, you can use the [resource detection processor](https://app.gitbook.com/s/gmiOMzBfoNFwmKJFHMcJ/integrations/processors/resource-detection).

{% hint style="info" %}
**NOTE**

Cluster name detection is available for Google GKE only. Support for Amazon EKS and\
Azure AKS is coming soon.
{% endhint %}

Add a processor to the source side of the pipeline by clicking on the processor icon (It can be found\
between the source icon and the destination icon).

Choose "Add Processor" and search for "Resource Detection".

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/Xh0GCYNp3S50N6pPanHJ/integrations-processors-resource-detection-image-1.png" alt="Bindplane docs - Kubernetes Monitoring - image 23"><figcaption></figcaption></figure>

Choose "Done" and then "Save".

#### Deploy Collectors

Once the configurations are created, you can move on to deploying agents.

**Retrieve YAML Manifests**

On the Collectors page, select the "Install Collector" button.

Choose the Kubernetes Node platform and the Kubernetes Node configuration you created earlier.

Select "Next" and you will be presented with a `yaml` text box. Choose "Copy" and save the contents\
to a file named `bindplane-node-agent.yaml`

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/bDvWrEjiVjJbLyFako2E/deployment-kubernetes-collector-install-image-2.png" alt="Bindplane docs - Kubernetes Monitoring - image 24"><figcaption></figcaption></figure>

Repeat these steps for the Cluster and Gateway agents. Save their `yaml` output to files named`bindplane-cluster-agent.yaml` and `bindplane-gateway-agent.yaml`.

**Kubectl Apply**

With all three manifests saved, you can apply them with a single command:

```bash
kubectl apply \
    -f bindplane-node-agent.yaml \
    -f bindplane-cluster-agent.yaml \
    -f bindplane-gateway-agent.yaml
```

The output will look like this:

```kubectl
namespace/bindplane-agent created
serviceaccount/bindplane-agent created
clusterrole.rbac.authorization.k8s.io/bindplane-agent created
clusterrolebinding.rbac.authorization.k8s.io/bindplane-agent created
service/bindplane-node-agent created
service/bindplane-node-agent-headless created
configmap/bindplane-node-agent-setup created
daemonset.apps/bindplane-node-agent created
namespace/bindplane-agent unchanged
serviceaccount/bindplane-agent unchanged
clusterrole.rbac.authorization.k8s.io/bindplane-agent unchanged
clusterrolebinding.rbac.authorization.k8s.io/bindplane-agent unchanged
deployment.apps/bindplane-cluster-agent created
namespace/bindplane-agent unchanged
serviceaccount/bindplane-agent unchanged
clusterrole.rbac.authorization.k8s.io/bindplane-agent unchanged
clusterrolebinding.rbac.authorization.k8s.io/bindplane-agent unchanged
service/bindplane-gateway-agent created
service/bindplane-gateway-agent-headless created
statefulset.apps/bindplane-gateway-agent created
```

The following resources are created

* Namespace: `bindplane-agent`
* RBAC
  * Service Account: `bindplane-agent`
  * Cluster Role: `bindplane-agent`
  * Cluster Role Binding: `bindplane-agent`
* Node Agent
  * clusterIP service: `bindplane-node-agent`
  * clusterIP service (headless): `bindplane-node-agent-headless`
  * DaemonSet: `bindplane-node-agent`
* Cluster Agent
  * Deployment: `bindplane-cluster-agent`
* Gateway Agent
  * clusterIP service: `bindplane-gateway-agent`
  * clusterIP service (headless): `bindplane-gateway-agent-headless`
  * DaemonSet: `bindplane-gateway-agent`

```kubectl
NAME                                          READY   STATUS    RESTARTS   AGE
pod/bindplane-cluster-agent-56dc56b78-fv2nx   1/1     Running   0          5m52s
pod/bindplane-gateway-agent-0                 1/1     Running   0          5m51s
pod/bindplane-gateway-agent-1                 1/1     Running   0          5m35s
pod/bindplane-node-agent-2dbtb                1/1     Running   0          5m52s
pod/bindplane-node-agent-4m5dl                1/1     Running   0          5m52s
pod/bindplane-node-agent-7z6bc                1/1     Running   0          5m52s
pod/bindplane-node-agent-d4xcw                1/1     Running   0          5m52s
pod/bindplane-node-agent-qfczn                1/1     Running   0          5m52s
pod/bindplane-node-agent-r75rt                1/1     Running   0          5m52s
pod/bindplane-node-agent-rjk54                1/1     Running   0          5m52s
pod/bindplane-node-agent-s94kf                1/1     Running   0          5m52s
pod/bindplane-node-agent-sxr4g                1/1     Running   0          5m52s
pod/bindplane-node-agent-x67r8                1/1     Running   0          5m52s
pod/bindplane-node-agent-xlfxs                1/1     Running   0          5m52s
pod/bindplane-node-agent-zjthj                1/1     Running   0          5m52s

NAME                                       TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
service/bindplane-gateway-agent            ClusterIP   10.112.11.20    <none>        4317/TCP,4318/TCP   5m52s
service/bindplane-gateway-agent-headless   ClusterIP   None            <none>        4317/TCP,4318/TCP   5m52s
service/bindplane-node-agent               ClusterIP   10.112.11.166   <none>        4317/TCP,4318/TCP   5m54s
service/bindplane-node-agent-headless      ClusterIP   None            <none>        4317/TCP,4318/TCP   5m53s

NAME                                  DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
daemonset.apps/bindplane-node-agent   12        12        12      12           12          <none>          5m53s

NAME                                      READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/bindplane-cluster-agent   1/1     1            1           5m53s

NAME                                                DESIRED   CURRENT   READY   AGE
replicaset.apps/bindplane-cluster-agent-56dc56b78   1         1         1       5m53s

NAME                                       READY   AGE
statefulset.apps/bindplane-gateway-agent   2/2     5m52s
```

Once the agents are deployed, they will appear on the Agents page. Agents are named with the following\
convention:

* Node agents take the name of the node they are running on
* The Cluster agent takes the name of the underlying pod
* Gateway agents take the name of the underlying pod

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/1xHBGffuWDnEw1ZLOPMc/deployment-kubernetes-collector-install-image-3.png" alt="Bindplane docs - Kubernetes Monitoring - image 25"><figcaption></figcaption></figure>

**Initial Configuration Rollout**

With the collectors connected, you must perform the initial rollout of the configurations.

Navigate to the Configurations page and select your Gateway configuration. Select the "Start Rollout"\
button. This will push the first version of the configuration to the collectors.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/D3deOON2VVfYUJmfaAq5/how-to-guides-kubernetes-kubernetes-monitoring-image-26.png" alt="Bindplane docs - Kubernetes Monitoring - image 26"><figcaption></figcaption></figure>

Navigate to the Node and Cluster configurations and trigger their initial rollout.

Once the configurations are rolled out, give them ten minutes to start displaying throughput measurements.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/Oa9oZbz2Kgyy2s9F05FZ/how-to-guides-kubernetes-kubernetes-monitoring-image-27.png" alt="Bindplane docs - Kubernetes Monitoring - image 27"><figcaption></figcaption></figure>

Click on an individual collector and select "Recent Telemetry" to view recent logs and metrics.

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/pXFLaYkYsBPZMdVPkGqf/how-to-guides-kubernetes-kubernetes-monitoring-image-28.png" alt="Bindplane docs - Kubernetes Monitoring - image 28"><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/BTPEeZNd5Ud1eWhwfCjZ/how-to-guides-kubernetes-kubernetes-monitoring-image-29.png" alt="Bindplane docs - Kubernetes Monitoring - image 29"><figcaption></figcaption></figure>

If the collector does not have recent telemetry, try selecting a different one. If activity in the cluster\
is low, recent telemetry may not be available on every collector right away.

### Security

Each agent manifest has a secret key that is used for authentication to Bindplane. If you intend to commit the manifest to git, you should first update the secret key environment variable to use a [Kubernetes Secret](https://kubernetes.io/docs/concepts/configuration/secret/).

```yaml
spec:
  template:
    spec:
      containers:
        - name: opentelemetry-container
          env:
            - name: OPAMP_SECRET_KEY
              value: YOUR_SECRET_KEY
```

You can create a secret and reference it.

```bash
kubectl -n bindplane-agent create secret generic \
  bindplane-agent \
  --from-literal=secret-key=YOUR_SECRET_KEY
```

```yaml
spec:
  template:
    spec:
      containers:
        - name: opentelemetry-container
          env:
            - name: OPAMP_SECRET_KEY
+             valueFrom:
+               secretKeyRef:
+                 name: bindplane-agent
+                 key: secret-key
```

Once the secret value is removed from the manifest, it can be safely committed to git.

### Troubleshooting

**Collectors do not appear on the Collectors page**

If the agent pods are running, but not appearing on the Collectors page, make sure your Bindplane server's remote URL parameter is set correctly.

If operating Bindplane on Linux, check the configuration at `/etc/bindplane/config.yaml`.

```yaml
network:
  remoteURL: http://bindplane.corp.net:3001
```

If using Helm to operate Bindplane on Kubernetes, make sure the `config.remote_url` value is correct.\
The Helm chart will set this value to the clusterIP in the Bindplane server's namespace, if it is not set explicitly.

```helm
config:
  remote_url: ws://bindplane.bindplane.svc.cluster.local:3001
```

In either case, the remote URL must resolve the Bindplane server and should be reachable by the agents.

If the remote URL appears to be correct, make sure it is correct in the agent manifest.

In this example, the remote URL `https://app.bindplane.com:3001` will result in an OpAMP endpoint with value `wss://app.bindplane.com:3001/v1/opamp`. The OpAMP endpoint is derived from the Bindplane remote URL setting.

```yaml
spec:
  template:
    spec:
      containers:
        - name: opentelemetry-collector
          env:
            - name: OPAMP_ENDPOINT
              value: wss://app.bindplane.com/v1/opamp:3001
```

### Frequently Asked Questions

**Q: Can I modify the manifests?**

**A:** Yes. You may want to adjust the cpu and memory resource request and limits, as well as affinity rules or pod priority class. You should adjust the manifests to fit your environment.

**Q: Can Bindplane Collectors be installed with Helm?**

**A:** Helm is not supported for collector installations. If you are interested in Helm support, please reach out to us through [support channels](https://app.gitbook.com/o/VImJSKtARNoRLNmMk5Yg/s/qsYYr4wUz1dij8xi2kaZ/). We would love to have your feedback.

**Q: Can Bindplane Collectors be installed with the OpenTelemetry Operator?**

**A:** The [OpenTelemetry Operator](https://github.com/open-telemetry/opentelemetry-operator) is not supported for agent installation. The operator only recently added support for OpAMP. We are following the development closely and look forward to supporting the operator in the future.

**Q: Is it safe to commit the agent manifests to git?**

**A:** Follow the [security](#security) section before committing the manifests to git.

**Q: Can I use ArgoCD or Flux to manage the agent deployments?**

**A:** Yes. If you have existing tooling in place for managing resources within your cluster, we encourage\
that you have them handle the agent installation.