F5 CIS IngressLink attaching WAF policy on the big-ip through the CRD ?

Ok I tested it and actually even with the community edition it works but sort of 😅 One small issue is the community edition returns 404 error when sending health monitor request to / without hostname and ingresslink attaches http monitors as it is meant to for the F5 Networks nginx version that has a default response page with 200 code. Also IngressLink creates F5 VIP that is just layer 3/4 without HTTP profile, so this explains a lot!

This feature is meant where F5 is Tier 0 and just provides basic protections like Global AFM DOS, AFM rules, TCP profile cookie security etc. It seems the main features like WAF (Nginx AppProtect ) , SAML and OAUth authentication/authorization in that case will be on the Nginx Plus (not the community opensource one) Ingress

apiVersion: v1
kind: Service
metadata:
  name: nginx-ingress-ingresslink
  namespace: ingress-nginx
  labels:
    app: ingresslink
spec:
  ports:
  - port: 80
    targetPort: 80
    protocol: TCP
    name: http
  selector:
    app: nginx-ingress
---
apiVersion: "cis.f5.com/v1"
kind: IngressLink
metadata:
  name: nginx-ingress
  namespace: ingress-nginx
spec:
  virtualServerAddress: "xxxx"
  host: demo.localdev.me
#  iRules:
#   - /Common/nginx-ingress
  selector:
    matchLabels:
      app: ingresslink