Capabilities Testing and Convenience Scripts

[qdzlug]

Currently, we provide a script named testcap.sh that is intended to verify that the K8 installation being tested meets the minimum requirements for MARA.

These requirements are:

• Persistent Volume support (storage)
• Egress IP support (K8 "loadbalancer")

In the event that the K8 installation does not have these features we provide a convenience script kubernetes-extras.sh that will try and install metallb and/or nfsvolumes to address this issue for the user. (Note that although we have a project directory for kubevip it is not currently working correctly.)

Over these last several months it has become apparent that the workstation based K8 distributions all provide some sort of workaround for storage and egress. This makes me question the logic of keeping the deployment option for these extras in the repository.

Additionally, the testcap.sh script has been shown not to work in some instances (for example, under minikube).

My plan for moving forward is:

• Deprecate the testcap.sh script; the script will echo a warning message noting that it is deprecated and will be removed in the future. Following that warning, the script will attempt to run as designed.
• Remove the kubevip project directory immediately; since this was never fully completed there is no reason to keep it around.
• Deprecate the kubernetes-extras.sh script in a manner similar to testcap.sh; that is, echo a warning and note that it will be removed at some point in the future.

Happy to entertain other thoughts on this.

[qdzlug]

Part of the preparation for NGINX Sprint around MARA is in making sure that we maintain the focus of the project, and when held up against that criteria the scripts and Pulumi code noted above fall outside that focus.

It seems reasonable to assume that anyone who uses MARA and wants to deploy one of our "kubeconfig" deployments (ie, not the full infrastructure deployment) will be able to ensure that their K8 installation meets the minimum requirements (ie, egress IP and PV support).

Currently putting in a PR to go ahead with the deprecation / removal.

[qdzlug]

PR is #159