Camunda 8: Container based deployment : Community version: Camunda:8.9.0-alpha1 failed to start pod

Camunda 8 Topics
1

Hi Team,

We are using container based deployment for camunda:8.9.0-alpha1 from camunda website.

This is a modified version of the Camunda Platform Helm chart, customized for:

  • Cluster: int0som-staging
  • Namespace: camunda-poc
  • Version: Camunda 8.8.0 (stable)
  • Configuration: Non-production, no Identity, no Web Modeler, no PostgreSQL

and we are getting below exceptions-

log for camunda-helm-zeebe-0
Error from server(Bad request): container orchastration in pod camunda-helm-zeebe-0 is waiting to start ContainerCreating

Events:
Warning FailedAttachVolume attachdetach-controller AttachVolume.Attach failed for volume “pvc-5c0b54b5-3513-436c-a49e-be4e1c169999” : Volume attachment is being deleted.

Warning FailedCreate statefulset/camunda-helm-zeebe creat camunda-helm-zeebe-0 in stateful camunda-helm-zeebe failed error: pod “camunda-helm-zeebe-0” is invalid : spec.volumes[1].secret.secretName: required value

Can you suggest if we are missing any configuration before starting the application?

Thanks,

Pradip Patil

2

Hi @Pradip_Patil - is there a reason you are trying 8.9-alpha1 instead of the stable 8.8 release? 8.9-alpha1 is a very, very early release and I would expect there to be significant issues with it still.

Also, just to avoid any confusion, there is no “Community version” of Camunda 8. The entire source is available under a “source-available” license. All of Camunda 8 starting with 8.6 requires a license to run in production. Camunda does offer free licenses for development, testing, non-profits, personal use, etc. - you can apply for a non-commercial license here.

1 Like