R&D: Running Black Duck on clusters with IPv6 disabled

Versions of Black Duck previous to version 2018.11.0 did not run in cluster environments where IPv6 was disabled. The root cause of this issue was that Tomcat, a component of Black Duck, malfunctioned when IPv6 was disabled.

Black Duck 2018.11.0 has updated Tomcat images that are happy without IPv6 enablement. This is a small patch with a couple of minor YAML modifications, and the CRD for creation is below.

If you aren't willing to upgrade your Black Duck instance to 2018.11.0 but need to run where IPv6 is disabled, you can follow the directions, below.

Note: The container configuration referenced below is intended only for POCs or customers wanting to experiment with the 'latest' IPv6 changes. They are provided as a convenience for customers that want to test this configuration and validate production readiness for clusters that disable IPv6.

{
        "apiVersion": "synopsys.com/v1",
        "kind": "Hub",
        "metadata": {
                "clusterName": "",
                "name": "hub-test-a"
        },
        "spec": {
                "namespace": "hub-test-a",
                "backupSupport": "No",
                "certificateName": "default",
                "environs": [
                        {
                                "key": "IPV4_ONLY",
                                "value": "1"
                        },
                        {
                                "key": "BLACKDUCK_HUB_SERVER_ADDRESS",
                                "value": "0.0.0.0"
                        }
                ],
                "dbPrototype": "empty",
                "dockerRegistry": "gcr.io",
                "dockerRepo": "saas-hub-stg/blackducksoftware",
                "hubVersion": "2018.11.0",
                "flavor": "small",
                "hubType": "worker",
                "imagePrefix": "blackduck",
                "imageTagMap": {
                        "authentication": "2018.11.0",
                        "cfssl": "1.0.0",
                        "documentation": "2018.11.0",
                        "hub-authentication": "2018.11.0",
                        "hub-scan": "2018.11.0",
                        "jobrunner": "2018.11.0",
                        "logstash": "1.0.0",
                        "nginx": "1.0.0",
                        "postgres": "1.0.0",
                        "registration": "2018.11.0",
                        "scan": "2018.11.0",
                        "solr": "1.0.0",
                        "webapp": "2018.11.0",
                        "webserver": "1.0.0",
                        "zookeeper": "1.0.0"
                }
        }
}

Thanks to our Pivotal partners for helping test this.