Config safety feature should retain last working configuration and reapply on failure

[mrajagopal]

Is your feature request related to a problem? Please describe.
A customer tried to apply an incorrect traffic-splitting configuration.
The only protects against configurations that pass NIC's internal validators but are subsequently rejected by Nginx, and does not provide rollback for configurations rejected by NIC's validators themselves.

Describe the solution you'd like
Ideally, when a faulty configuration is rejected, the system is expected to keep running with last working configuration

Describe alternatives you've considered
Using k8s infra tools to manage such configuration application and rollback

[github-actions]

Hi @mrajagopal thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

If your issue concerns any of the enterprise features please open a ticket with F5 directly (For NGINX Plus customers NGINX Ingress Controller (when used with NGINX Plus) is covered by the support contract.)

Cheers!