Working with trino-operator and podOverrides

[dshershov]

Hello team!
i'm trying to figure it out how to work with podOverrides
I have a next code:

apiVersion: trino.stackable.tech/v1alpha1
kind: TrinoCluster
metadata:
  name: trino
  namespace: dwh
spec:
  image:
    productVersion: "414"
    stackableVersion: "23.7"
  clusterConfig:
    catalogLabelSelector:
      matchLabels:
        trino: trino
  coordinators:
    roleGroups:
      default:
        podOverrides:
          spec:
            initContainers:
            - name: init-ranger
              image: hub.nexus-pvt.com/stackable/trino:414-stackable23.7
...

My initContainer doesn't starting with pod
Logs with operator and trino svc are empty.

2023-09-05T14:10:16+04:00 2023-09-05T10:10:16.487164Z  INFO reconciling object{object.ref=TrinoCluster.v1alpha1.trino.stackable.tech/trino.dwh object.reason=object updated}: stackable_trino_operator::controller: Starting reconcile
2023-09-05T14:10:16+04:00 2023-09-05T10:10:16.888052Z  INFO stackable_operator::logging::controller: Reconciled object controller.name="trinocluster.trino.stackable.tech" object=TrinoCluster.v1alpha1.trino.stackable.tech/trino.dwh

Can you help me with configure init container to the trino cluster?
k8s cluster with 1.23.6 version
Trino, commons, secret operators was been updated from 23.4.1 to 23.7.0

Thanks a lot!

[Jimvin]

Hi,
If I try to reproduce this the init container fails to start and I see this error message:

kubectl --namespace dwh logs trino-coordinator-default-0 -c init-ranger
ERROR: Config file is missing: /stackable/conf/config.properties

That's to be expected since I'm not passing any configuration to this pod. Are you deploying the Stackable Trino image as the init container? Perhaps you intended to start a different container image. What is it that you want the init container to do?

Note that K8s 1.23 is no longer supported on 23.7.0, 1.24 and upwards are supported. I tried reproducing this issue on both 1.23 and 1.25 and saw no difference in behaviour.

Cheers,
Jim

[dshershov]

I need to prepare to working with ranger and try to install ranger-trino-plugin

[Jimvin]

Stackable has been working on an Open Policy Agent (OPA) authoriser plugin as an alternative to Apache Ranger. This could a suitable alternative to implementing the Ranger plugin. You can find more details in the docs here - https://docs.stackable.tech/home/nightly/trino/usage_guide/security#_authorization

May we close this issue since the podOverrides appear to be working as expected?

[dshershov]

Oh, I found the problem. I updated operator to the new version, but CRD was not updated without redeploy.
After redeploy I see that podOverrides was enabled for me
Thanks for OPA as an alternative but we need to work with ranger in other components