nodeselector | small bookmarklet to help you find Xpaths

You ran kubeseal against the wrong Kubernetes cluster or you tried to edit the name or namespace after encrypting without enabling those in the encryption mode. More likely the first.

The error says 'cannot create /var/lib/rabbitmq/mnesia/rabbit@reana-message-broker-5f45f797ff-cs79m.pid: Permission denied'. Try providing write permission for /var/lib/rabbitmq/mnesia/ directory.

For the ELK stack to work you need all three PersistentVolumeClaim's to be bound as I recall. Instead of creating 1 30 GB of PV create 3 of the same size with the claims and then re-install. Other nodes have unmet dependincies.

Also please do not handle the volumes by hand. There are guidelines to deploy dynamic volums. Use OpenEBS for example. That way you wont need to worry about the pvc's. After giving the pv's if anything happens write again with your cluster installation process.

I was wrong obviously, in this particular problem, filesystems and cgroups take role and the main problem of this is an old problem. From 5.2.1 to 8.0.0. Reinstall the chart by pulling the chart. Edit values file and definitely change the container version. It should be fine or create another error log stack.

There were two issues with the deployment setup:

The nodeSelector specified in the Deployment manifest was using wrong label

As @Brian de Alwis pointed out in the comments section, this PR #11189 should resolve the above issue.

You can try the v1.20.0-beta.0 release with this fix. Additionally, a stable v1.20.0 version is now available.

I was able to resolve the issue. The issue was using configmap in place configMap in deployment.yaml:

You are running Jenkins itself as a container. Therefore the docker command line application must be present in the container, not the host.

Easiest solution: Use a Jenkins docker image that contains the docker cli already, for example https://hub.docker.com/r/trion/jenkins-docker-client

Your approch seems right. Another solution could be to include the jar on the Docker image but I think it's not possible right ?

You could just use an emptyDir instead of a VolumeClaim.

Last one, I would have download the jar before waiting for ZooKeeper to gain some time.

The proper way to do this is to build "multi-arch" images, e.g. so that your container image contains binaries for multiple architectures. See e.g. Building Windows Server multi-arch images and Docker: Multi-arch build and images, the simple way - but it still seem to be an "experimental feature". A drawback with this is that the images will end up to be bigger, this is not so welcome if you want good elasticity (e.g. be able to quickly scale up with more pods) - this is especially true for windows images.

Alternatively, you need to use a separate Deployment for each architecture and use different Taints and Tolerations on the nodes and the pods.

You can keep this relatively clean by using kubectl kustomize and only override a small part of the manifests.