> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/deployment/upgrading-connectware/on-kubernetes/to-2-4-0-on-kubernetes.md).

# Upgrading Connectware to 2.4.0 (Kubernetes)

How to upgrade Connectware to version 2.4.0 on Kubernetes.

Connectware 2.4.0 adds the `caFile` property to the OPC UA Server, refreshes the Admin UI, and updates Node.js versions across Connectware services. For a complete list of changes, see the [2.4.0 changelog](https://docs.cybus.io/2-6-1/deployment/upgrading-connectware/on-kubernetes/pages/veQnb7pmTbxcaG8seqYD#connectware-2.4.0).

{% hint style="warning" %}

## Check your upgrade path

The steps in this guide apply to specific setups. Before you continue, check [Connectware Upgrade Paths](/2-6-1/deployment/upgrading-connectware/upgrade-paths.md) to determine which upgrades and steps apply to your installation.
{% endhint %}

{% stepper %}
{% step %}

## Upgrading Connectware to 2.4.0

Follow the instructions in [Upgrading Connectware (Kubernetes)](/2-6-1/deployment/upgrading-connectware/on-kubernetes.md) to upgrade to version 2.4.0.
{% endstep %}

{% step %}

## OPC UA Server with Custom PKI: Add caFile

This step applies if you are running OPC UA Server services with a **custom PKI** — that is, you have configured your own `certificateFile` and `privateKeyFile` signed by your organization's CA. If you do not use the OPC UA Server, skip this step.

Previously, the only way to provide your CA certificate to the OPC UA Server was to manually place it in `/app/.config/node-opcua-default-nodejs` inside the container. Connectware 2.4.0 introduces the `caFile` property as the recommended way to provide the CA certificate to the OPC UA Server.

To migrate, add `caFile` to the `properties` of your OPC UA Server resource in each affected service commissioning file, pointing to the path of your CA certificate inside the container:

{% code lineNumbers="true" %}

```yaml
resources:
  opcuaServer:
    type: Cybus::Server::Opcua
    properties:
      protocol: OpcuaServer
      certificateFile: /path/to/server.crt
      privateKeyFile: /path/to/server.key
      caFile: /path/to/ca.crt
```

{% endcode %}

For more information, see [CA Certificate](/2-6-1/connectors/servers/opc-ua-server.md#ca-certificate).
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cybus.io/2-6-1/deployment/upgrading-connectware/on-kubernetes/to-2-4-0-on-kubernetes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.