Jakub Jarosz

> Can we add a README for the new `externalname-services` example files? It's WIP (work in progress)

Same here, running on M1. Please consider improving UX by possibly returning error explicitly and stopping execution. Successful messages after failing conditions are misleading. Cheers!

test log: ```shell I1003 13:52:25.597291 1 event.go:298] Event(v1.ObjectReference{Kind:"VirtualServer", Namespace:"default", Name:"cafe", UID:"eb5fa829-4f39-4cd1-973a-78282d2d76d2", APIVersion:"k8s.nginx.org/v1", ResourceVersion:"277941", FieldPath:""}): type: 'Warning' reason: 'AddedOrUpdatedWithWarning' Configuration for default/cafe was added or updated with warning(s): VirtualServerRoute default/coffee doesn't...

Employing `regexp2` package that uses Perl5 / .NET compatible regex implementation engine solves the path validation problem.

Hi @nixx, Thanks for reporting the issue. We are planning to make the module importable, so packages could be used by referencing `v3`.

@nixx which packages do you want to import to your module? for the [ref](https://go.dev/doc/modules/layout#multiple-packages)

Work on this item can be resumed when we get more information from @nixx, and possible target V4 (version 4.0.0) of the `Kubernetes-ingress` module.

Hi @mrajagopal, I want to ask a more general question about what is the intention behind this PR?

An idea that may be worth considering: We have many functions in the `main` that call `log.Fatal` in case of an error. It maybe worth considering to the `must` prefix...

References: **CIS Hardening and verification OSS tools** [**Docker Bench for Security**](https://github.com/docker/docker-bench-security) is an open source script that audits containers according to the CIS benchmark’s best practices. It performs tests based...