tmyhu

The error message may not be misleading. I've run into the same after updating KubeRay operator to v1.1.0 and no updates to the ray cluster config were applied anymore e.g....

On a similar note, our deployment also broke due from #341 to the environment variable PREFECT_API_DATABASE_CONNECTION_URL now being always set in the deployment whether postgresql is enabled or not. Previously...

Awesome, that looks great. Thanks for letting me know @mitchnielsen

This is an example pod that uses one of the exempt images but still raises the violation: ``` apiVersion: v1 kind: Pod metadata: labels: beat.k8s.elastic.co/name: filebeat8 beat.k8s.elastic.co/version: 8.13.2 common.k8s.elastic.co/type: beat...

So are you saying this is intentional since the CEL version is now being updated to behave the same? It would sure be useful to define exceptions for hostNetwork via...

> > We are seeing a similar issue with v1.31.0 producing a TLS handshake timeout and referencing the ELBs DNS name instead of the name listed in the kubeconfig >...

From my perspective, a permanent solution via the cluster.Spec.API.PublicName would be preferred but the flag should work as well. Thanks!

@mitchnielsen it looks good to me, but won't make any difference for our use case since we are using SQLite. I assume that's not something you really want to support...

Thanks, I can confirm that the query works as expected if I use POST instead of GET in the Dev Tools console ie: ``` POST /my-index/_search { "query": { "match":...