Sarah Henkens

The `HandleCallback` function seems to be impacted by this bug as well

I'm having the same problem with setting up a connector for Okta

Thoughts on adding a helm values to wrap the CRD that can be disabled from the `values.yaml`? With some CD systems like ArgoCD, we can't pass in command line arguments...

I'm seeing the same problem on my deployments. @millerjl1701, where you able to resolve this?

When trying to manually run the life cycle probe from the pod: ```bash $ /lifecycle/tools/arangodb_operator lifecycle probe --endpoint=/_admin/server/availability --ssl --auth {"level":"info","path":"/secrets/cluster/jwt/token","time":"2021-09-13T00:19:48Z","message":"Try to use file"} {"level":"info","token":"token","time":"2021-09-13T00:19:48Z","message":"Using JWT Token"} {"level":"error","error":"Unexpected code: 503...

Maybe checking for the cluster endpoints is a better mechanism for readiness? ```bash $ /lifecycle/tools/arangodb_operator lifecycle probe --endpoint=/_api/cluster/endpoints --ssl --auth {"level":"info","path":"/secrets/cluster/jwt/token","time":"2021-09-13T00:42:25Z","message":"Try to use file"} {"level":"info","token":"token","time":"2021-09-13T00:42:25Z","message":"Using JWT Token"} {"level":"info","time":"2021-09-13T00:42:25Z","message":"Check passed"} ```

Chiming in here as well, this is a hard-blocker for our team to adopt this operator since we use ArgoCD

Bumping up on this. We are having the same issue

@mauriciopoppe I think if we do a fresh docker build. It should pick up the latest node 16 or node 18 versions with the security patches included. Just need to...

Still pending