Björn Pedersen

The seen modules are cached e.g. for the circular dep. check. The problem is that bin/project is seen internally as a module 'project', while it is not a module resolvable...

I think the correct logic would be: if a specified path 'xxx/yyy' is also importable as 'xxx.yyy', then it is a module to add, otherwise it is some standalone file...

https://github.com/rancher/rancher/blob/v2.6.7/pkg/auth/providers/keycloakoidc/keycloak_client.go#L167-L174 seems to be the problem with fresh keycloak install > keycloak17. The standard url does not contain the auth prefix anymore. Related to #38480, duplicated by #38683

Looking at the policy I think you are not granting enough rights for the console, see https://github.com/minio/minio/issues/14099

Seems like https://github.com/minio/pkg/pull/4 did only add the names, but no usage of the tags?

Followup: To me it seems the console queries opa (via minio) almost correctly (I see the queries arriving at opa), just for listing bucket content there is a logical flaw:...

I can confirm this happens (same versions) here too. Interesting points: 2 deployments with separate zones and zone filters. I suspect it is related to #3976 and followup changes.

I guess the problems stems from these commits: https://github.com/kubernetes-sigs/external-dns/pull/3976/commits/714078dc95db9514e4613502f42f7efe7c0db10e and https://github.com/kubernetes-sigs/external-dns/pull/3976/commits/714078dc95db9514e4613502f42f7efe7c0db10e The field name changes and that change is likely not correctly reflected in the bitnami chart.

I think this issues indicates that the release changelog is not highlighting such changes as breaking. It only shows the pull request title `RFC2136: Allow multiple zones` , without mentioning...

Further inspection indicates that it is a problem that the zone matching does not work correctly anymore. For now staying on 0.14.0 is working.