There is a known issue where updating a BackendConfig resource
using the v1beta1 API removes an active Google Cloud Armor
security policy from its service. If you do not configure Google Cloud Armor
on your Ingress resources via the BackendConfig, then this issue does not affect your clusters.
Dropped Cloud Armor security policies must be manually reattached.
No tracked CVEs