After OCP settled then next menu is go Camunda.
Here is the thing:
-Hardware perspective is minimal, mine is laptop i5 ancient gen 5th with 16GB memory and 512 GB SSD.
-Installed Openshift is CRC (CodeReady Container) with one node cluster , it's bare minimum for OCP. Well, can't agree more considering minimal hardware :)
Following installation step for Camunda - Openshift in their community website looks stright forward.
-Prepare Helm Chart for Openshift
-Add some privileges according to Camunda required
-Install Camunda from Helm dashboard
Ok tinkering time. Add some privilege to deal with OCP security framework, a scc.privileged and scc.anyuid is necessity for user and system access level.
Install Camunda using Helm Chart which is easy done using Openshift UI menu.
Then the hard part is after successful install it will show some pods unable to run.
What is wrong? apparently CRC local version is very limited in term of cluster size and security configuration.
After reading similar problem with installation in CRC I came to conclusion, it is all about security parameter unsuited Helm Chart's provided yaml. Some adjustment must be made.
fsGroup and runAsUser should assign id in specific range 1000660000 - 1000669999,
SeLinuxOptions should follow exactly CRC suggested (as shown in pod event history). Mine should at level: s0:c26,c5 (whatever that means).
When above adjustment made, crate/install will go smooth and pods running as shown in topology or workload.
Beautiful
Ah, wait. most of them are in pending state, not really beautiful.
Then event history showed me this.
Alas. This CRC will it up all my resources if I added/deployed an application.
Sadly. Ok thank you, good bye OCP see you later.
References:
https://docs.camunda.io/docs/self-managed/setup/deploy/openshift/redhat-openshift/
