Have another look at OpenShift support

[hardillb]

Description

Also have another look at the postgresql chart to pick a version that will install on OpenShift

Allow default uid/gid to be supplied by the k8s rather than had coded 1000. This is for the forge, file-server and stack containers.

Requested By

• Customer name and/or link to HubSpot contact

[ppawlowski]

Regarding the possibility of setting custom uid/gid:

• our Helm chart allows specifying custom securityContext settings for pods through the forge.podSecurityContext, forge.broker.podSecurityContext, and forge.fileStore.podSecurityContext chart values. This feature has been available for some time
  * recent update to the Helm chart introduced the ability to set an empty (null) podSecurityContext.
• in kubernetes driver, I see where it is configured. Not sure how user could provide those values for NR instances, though. At this moment we provide a workaround for openshift platform exclusively. @hardillb let me know if and how can I help here

Regarding FF on OpenShift using Helm chart -I successfully installed the FlowFuse platform on an OpenShift 4.x cluster using the latest Helm chart version and the minimum configuration required. Minimum setup includes local postgres database. At this point, I do not see any issues between our chart/application and openshift.

[hardillb]

The best approach would be to add the required section under a key in the driver.options section of the flowforge.yml file (configmap).

This is passed to the driver and can then be used when building the instance Deployment.

One thing to keep in mind would be the Persistent storage addon to make sure any mounted filesystem has the right permissions for the passed in uid/gid.