mark dittmer
@tkam8 feature request. CIS doesn't handle this logic in CRD. Possible to handle with different virtualServerName for transportserver. Example  workaround in place a ConfigMap?
@azzauzuaz going to address your question/issue first When using a CRD, CIS uses policies. The pool is associated to the policy. When a policy is used the virtual status will...
@Creat1v Network map will show as  This is expected behavior when using a VirtualServer CRD, OCP route. If you use a TransportServer no policy is created. TS adds the...
@cchriso BIG-IP is working correctly. Not a defect. Due to the policy when using layer 7 on BIG-IP.
At this time CIS is functioning correctly. Recommend using a TransportServer as an option. No policy is created and therefore the Virtual status will show green. This issue can be...
Requirement - Expose options to run CIS on the controller nodes. Must be configured via Helm Chart
CRD can not define the SNAT Pool, but only can reference a exist SNAT Pool in BIG-IP, or use automap
**Agree** we should add **"snat": "self"**, as a object in the CRD. Will create a Jira Action: - jira - PO to prioritize
CRD can not define the SNAT Pool, but only can reference a exist SNAT Pool in BIG-IP, or use automap
@kylinsoong at this time we dont plan to add "snat": "self", to the schema. Please use the alternative snat profile. AKA snat: "/Common/testsnat" Closing this issue out at this time.
@sebidude we released CIS 2.10.1 today. Please can you reach out me at [email protected] so i can prioritize other fixes/enhancements and know who you are. Thanks CIS PM
Thanks @vincentmli you are correct. @bukovjanmic can you check a few things. First check the VXLAN policy within BIG-IP. Mac sure you see FBD entries. If not please review CIS...