Some Octopus Cloud customers affected by parsing issue with ConfigMap on Kubernetes deployments

We are currently rolling out the fix to Cloud customers. Instances will be upgraded in their next maintenance window. If you are affected by this issue and want to expedite the upgrade, please contact support@octopus.com

A fix has been implemented and will be rolled out to affected cloud customers in their next maintenance window.

We have identified the issue with a recently released version of Octopus Server to cloud customers.
A recent change has caused config maps with multi-line variables, created via the Kubernetes containers deployment step, to fail. Config maps created by the dedicated Kubernetes config map step are not affected, nor config maps created by Raw YAML or Helm steps.
We are in the process of fixing this and will update the public issue with the fixed version: https://github.com/OctopusDeploy/Issues/issues/9221.

We are currently investigating the issue