Add possibility to specify custom image registry used by project pods

[ppawlowski]

Description

The goal of this task is to add a possibility to specify a custom container image registry where the project's images are stored.
This feature requires changes in both the Helm chart and the FlowFuse Kubernetes driver.

Requested By

https://app-eu1.hubspot.com/help-desk/26586079/view/233410279/ticket/252511200495/thread/14935179502

[dbruynb]

@ppawlowski , please check the code on line 86 https://github.com/FlowFuse/driver-k8s/blob/main/kubernetes.js#L86
Correct me if I'm wrong but I think a "/" should be added before "flowforge/node-red" --->>>${this._options.registry}flowforge/node-red`

[hardillb]

The registry can already be set with forge.registry in the helm file.

@dbruynb it's a little more complicated as it needs to not add the / if the registry value is empty

But also fully qualified container names can be set in the Stack definition under the Admin Settings.

So this would only apply to the default stack created on first startup.

[dbruynb]

Thanks @hardillb , I already set forge. Registry and can confirm that both FlowFuse and Postgres images get pulled with my custom registry. I can also conform that in flowforge.yml its listed under:

driver
  type: kubernetes
  options:
    registry:

I can't confirm what registry path is used for a nodered project node, I just can see the kervano policy blocks it.

So I trired adding a new stack but the frontend is not acecpting my full path with custom regstiry and ending with flowfuse/node-red

[hardillb]

@dbruynb I will check the regex that validates, but you may just be missing a tag name on the end. Try adding :latest

[hardillb]

@dbruynb OK, I know what the problem is, the regex doesn't like the 2 levels of path in container name.

I'll open a seperate issue against the k8s driver for that

[hardillb]

@dbruynb FlowFuse/driver-k8s#247

[hardillb]

Correct me if I'm wrong but I think a "/" should be added before "flowforge/node-red" --->>>${this._options.registry}flowforge/node-red`

@dbruynb also lines 644-648 in the kubernetes file handle adding the trailing / if required

https://github.com/FlowFuse/driver-k8s/blob/7138aed2c7204c274c51b8a100ee5f1a46a2262c/kubernetes.js#L644-L648

[ppawlowski]

@dbruynb @hardillb having all that, do we still think there is a need for a separate configuration parameter to specify a custom registry for projects (different from the one provided in forge.registry )?