Add overwriteSchema for route config

[titigmr]

Hello,

I need to modify some values in route config on openshift, but overwriteSchema is not available for all catalogs (database, ide, etc.).

Thank you!

[ihiverlet]

Hello @titigmr
There won't be a problem doing it for ide charts as we fully control them. However ,for other catalogs, the ingresses don't follow necessarily the same pattern as they depend on the chart. This means we can't provide a clean, generic way to achieve what you want unless we prefix the schema by the chart name for exemple: cloudbeaver/ingress.json,milvus/ingress.json ... which will result in a very verbose config file within onyxia.
What's the underlying need for this change ?

[titigmr]

Hello,

I need a custom configuration for all ingresses for OpenShift compatibility.

I prefer configuring ingresses rather than routes because there is a bug affecting some routes in certain charts (pgadmin and cloudbeaver for example), and the template for routes from the library chart is not available for all charts (for example, Airflow there are not route.yaml file).

This is the schema override that works for me in the IDE catalog:

- relativePath: ide/ingress.json
  content: |
    {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "title": "Ingress",
        "description": "Ingress parameters",
        "type": "object",
        "properties": {
            "enabled": {
                "description": "Enable Ingress",
                "type": "boolean",
                "const": true,
                "x-onyxia": {
                    "hidden": true,
                    "overwriteDefaultWith": "k8s.ingress"
                }
            },
            "hostname": {
                "type": "string",
                "form": true,
                "title": "Hostname",
                "x-onyxia": {
                  "hidden": true,
                  "overwriteDefaultWith": "{{project.id}}-{{k8s.randomSubdomain}}-0.{{k8s.domain}}"
               }
            },
            "userHostname": {
               "type": "string",
               "form": true,
               "title": "Hostname",
               "x-onyxia": {
                  "hidden": true,
                  "overwriteDefaultWith": "{{project.id}}-{{k8s.randomSubdomain}}-user.{{k8s.domain}}"
                  }
            },
            "annotations": {
               "type": "object",
               "title": "Ingress annotations",
               "description": "Annotations applied to the ingress/route resource",
               "default": {
                  "route.openshift.io/insecureEdgeTerminationPolicy": "Redirect",
                  "route.openshift.io/termination": "edge"
                 },
               "additionalProperties": {
                  "type": "string"
               },
               "x-onyxia": { "hidden": false }
            },
            "tls": {
                "type": "boolean",
                "const": false,
                "x-onyxia": {"hidden": true}
            }
       }
    }

I only want to disable TLS and add custom annotations.

Currently, the only way to modify TLS is via the overwrite schema, and there is also a bug with annotations which is not configurable by the onyxia api (issue).

[fcomte]

@titigmr what should be change in this repository ?

Do you want us to add an overwriteSchema for the object route inside this repository (indeed it is not exist) ?

[titigmr]

My issue is more general and applies to all catalogs, but it can also be turned into a discussion.

The OpenShift compatibility with routes doesn’t work very well for all charts, and some configurations are missing.

I think it’s better to use Ingress (OpenShift create routes based on Ingress). However, it is necessary to configure the Ingress with custom annotations and disable TLS . The overwriteSchema works well, but it generates a very large values.yaml because each chart (except charts on IDE catalog) uses a custom overwriteSchema.

Do you have any suggestions for this issue?

Thanks