Tony Dai

@mflendrich thanks for taking a look. The configuration we had was roughly: ```yaml kind: KongConsumer metadata: annotations: kubernetes.io/ingress.class: kong name: userA namespace: namespaceA username: user credentials: - credentials1A - credentials2A...

I've opened https://github.com/awslabs/amazon-kinesis-producer/pull/288 to properly pass on the log level from the main app to the daemon process. Open to any suggestions.

**Update**: I see our managed cluster has been updated to `v1.27.10-eks-508b6b3` and the managed platform version `eks.13`. In the reproduction example from my post, the `from.podSelector` rule is now working,...

@achevuru I think you might be misunderstanding my example (correct me if I am wrong): In my net policy I have an ingress rule for a CIDR range (not pod...

@achevuru Thank you, and yes, I understand the caveats

Another note for anyone else possibly facing this: For rules that allow all traffic to specific ports e.g. ```yaml ingress: - ports: - port: https protocol: TCP ``` Under the...

Hi, > didn't see a good reason to support all ports if no ports are defined in this case I would say that a good reason is that the NetworkPolicy...

Likewise for `zero_trust.access.users.list`. Believe some of the other clients like the golang one has the same issue. My temp workaround: ```python cf_users = [] cf_users_page = await cf_client.zero_trust.access.users.list(account_id='...') cf_users +=...