alonsocamaro

Found that when using Helm charts, at installing in CIS in the kube-system it is deployed just fine, without PSPs: ``` tanzu$ kubectl -n kube-system get pods NAME READY STATUS...

Initially this idea suggested using just node-label-selector but after talking with Bart Van Bos he showed me his concern that the node could actually not host the POD, hence I...

replied @trinaths via teams

Checking previous code I wrote, probably before this module existed, is as follows and worked reliably: ``` - name: "config-sync from master to ha-group" bigip_command: server: "{{ master }}" commands:...

I'm finding this issue with CIS 2.11 in a partner lab. In the case of CIS 2.11, the messages are different: `[ERROR] [CORE]Endpoints could not be fetched for service XXX...

Couldn't we just use Kubernetes API to check if the Primary CIS is Ready? This would simplify things greatly

Hi Rich When I triggered the error my setting use_namespaces is set to False so I was not expecting to have different routing domains. I would like to clarify if...

A non-cosmetic reason to implement pool-member-type=hostnetwork is because when using hostnetwork and the OVN CNI, we don´t need to create static routes to the cluster IPs, which might not be...

As a side note, when not using defaultTLS to avoid this issue and one of the Routes misses the embedded certificate, then it gets applied to one of the certificates...

For example, instead of: ``` extendedSpec: | baseRouteSpec: tlsCipher: tlsVersion: 1.2 ciphers: DEFAULT cipherGroup: /Common/f5-default extendedRouteSpec: - namespace: tenant1 vserverAddr: 10.8.3.130 vserverName: routetenant1 allowOverride: true - namespace: tenant2 vserverAddr: 10.8.3.132...