You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provide parameter to enable Connection Mirroring in TransportServer CR
Description
Expose a new parameter in TransportServer (and potentially also VirtualServer) to enable Connection Mirroring
Actual Problem
Customer is deploying CIS instances for their new OCP Clusters, and looking to use TransportServer CR to front their TCP apps becauso of its simple YAML format. Due to the nature of the app traffic, connection mirroring is mandatory, but it doesn't seem to be configurable in TransportServer CR.
Solution Proposed
Expose a new parameter in TransportServer CR to enable Connection Mirroring, which is already supported by the underlying Service_TCP class in AS3.
Alternatives
Switching to AS3 ConfigMap, which is harder for the customer's team to understand & craft.
Additional context
Customer is considering other Ingress solution/vendor if the AS3 ConfigMap is rejected by their ops team.
The text was updated successfully, but these errors were encountered:
@adityoari Please mail automation_toolchain_pm automation_toolchain_pm@f5.com this issue with required CIS configuration and resource examples to review at our end.
Title
Provide parameter to enable Connection Mirroring in TransportServer CR
Description
Expose a new parameter in TransportServer (and potentially also VirtualServer) to enable Connection Mirroring
Actual Problem
Customer is deploying CIS instances for their new OCP Clusters, and looking to use TransportServer CR to front their TCP apps becauso of its simple YAML format. Due to the nature of the app traffic, connection mirroring is mandatory, but it doesn't seem to be configurable in TransportServer CR.
Solution Proposed
Expose a new parameter in TransportServer CR to enable Connection Mirroring, which is already supported by the underlying Service_TCP class in AS3.
Alternatives
Switching to AS3 ConfigMap, which is harder for the customer's team to understand & craft.
Additional context
Customer is considering other Ingress solution/vendor if the AS3 ConfigMap is rejected by their ops team.
The text was updated successfully, but these errors were encountered: