# dev-ex-dashboard
# not ok 1 - /tmp/rhcop/05-08-2020-11-53/charts/dev-ex-dashboard/templates.yaml - Service/dev-ex-dashboard: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 2 - /tmp/rhcop/05-08-2020-11-53/charts/dev-ex-dashboard/templates.yaml - DeploymentConfig/dev-ex-dashboard: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 3 - /tmp/rhcop/05-08-2020-11-53/charts/dev-ex-dashboard/templates.yaml - Route/dev-ex-dashboard: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 4 - /tmp/rhcop/05-08-2020-11-53/charts/dev-ex-dashboard/templates.yaml - DeploymentConfig/dev-ex-dashboard: container 'dev-ex-dashboard' does not have an env named 'CONTAINER_MAX_MEMORY' which is used by the Red Hat base images to calculate memory. See: https://docs.openshift.com/container-platform/4.4/nodes/clusters/nodes-cluster-resource-configure.html and https://github.com/jboss-openshift/cct_module/blob/master/jboss/container/java/jvm/bash/artifacts/opt/jboss/container/java/jvm/java-default-options
# not ok 5 - /tmp/rhcop/05-08-2020-11-53/charts/dev-ex-dashboard/templates.yaml - DeploymentConfig/dev-ex-dashboard: container 'dev-ex-dashboard' is from ( ), which is an unknown registry.
# not ok 6 - /tmp/rhcop/05-08-2020-11-53/charts/dev-ex-dashboard/templates.yaml - DeploymentConfig/dev-ex-dashboard: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'app'
# not ok 7 - /tmp/rhcop/05-08-2020-11-53/charts/dev-ex-dashboard/templates.yaml - DeploymentConfig/dev-ex-dashboard: container 'dev-ex-dashboard' has no livenessProbe. See: https://docs.openshift.com/container-platform/4.4/applications/application-health.html
# not ok 8 - /tmp/rhcop/05-08-2020-11-53/charts/dev-ex-dashboard/templates.yaml - DeploymentConfig/dev-ex-dashboard: container 'dev-ex-dashboard' has no memory limits. It is recommended to limit memory, as memory always has a maximum. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers
# not ok 9 - /tmp/rhcop/05-08-2020-11-53/charts/dev-ex-dashboard/templates.yaml - DeploymentConfig/dev-ex-dashboard: container 'dev-ex-dashboard' has a volumeMount 'app-config' mountPath at '/opt/app-root/src/config'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 10 - /tmp/rhcop/05-08-2020-11-53/charts/dev-ex-dashboard/templates.yaml - DeploymentConfig/dev-ex-dashboard: replicas is 1 - expected replicas to be greater than 1 for HA guarantees.
# etherpad
# not ok 1 - /tmp/rhcop/05-08-2020-11-53/charts/etherpad/templates.yaml - Service/RELEASE-NAME-etherpad: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 2 - /tmp/rhcop/05-08-2020-11-53/charts/etherpad/templates.yaml - Deployment/RELEASE-NAME-etherpad: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 3 - /tmp/rhcop/05-08-2020-11-53/charts/etherpad/templates.yaml - Route/RELEASE-NAME-etherpad: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 4 - /tmp/rhcop/05-08-2020-11-53/charts/etherpad/templates.yaml - Deployment/RELEASE-NAME-etherpad: container 'etherpad' does not have an env named 'CONTAINER_MAX_MEMORY' which is used by the Red Hat base images to calculate memory. See: https://docs.openshift.com/container-platform/4.4/nodes/clusters/nodes-cluster-resource-configure.html and https://github.com/jboss-openshift/cct_module/blob/master/jboss/container/java/jvm/bash/artifacts/opt/jboss/container/java/jvm/java-default-options
# not ok 5 - /tmp/rhcop/05-08-2020-11-53/charts/etherpad/templates.yaml - Deployment/RELEASE-NAME-etherpad: container 'etherpad' is using the latest tag for its image (etherpad/etherpad:latest), which is an anti-pattern.
# not ok 6 - /tmp/rhcop/05-08-2020-11-53/charts/etherpad/templates.yaml - Deployment/RELEASE-NAME-etherpad: container 'etherpad' is from (etherpad/etherpad:latest), which is an unknown registry.
# not ok 7 - /tmp/rhcop/05-08-2020-11-53/charts/etherpad/templates.yaml - Deployment/RELEASE-NAME-etherpad: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'helm.sh/chart'
# not ok 8 - /tmp/rhcop/05-08-2020-11-53/charts/etherpad/templates.yaml - Deployment/RELEASE-NAME-etherpad: container 'etherpad' livenessProbe and readinessProbe are equal, which is an anti-pattern.
# not ok 9 - /tmp/rhcop/05-08-2020-11-53/charts/etherpad/templates.yaml - Deployment/RELEASE-NAME-etherpad: container 'etherpad' has no memory limits. It is recommended to limit memory, as memory always has a maximum. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers
# not ok 10 - /tmp/rhcop/05-08-2020-11-53/charts/etherpad/templates.yaml - Deployment/RELEASE-NAME-etherpad: container 'etherpad' has a volumeMount 'etherpad-data' mountPath at '/opt/etherpad-lite/var'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 11 - /tmp/rhcop/05-08-2020-11-53/charts/etherpad/templates.yaml - Deployment/RELEASE-NAME-etherpad: replicas is 1 - expected replicas to be greater than 1 for HA guarantees.
# jenkins
# not ok 1 - /tmp/rhcop/05-08-2020-11-54/charts/jenkins/templates.yaml - Service/jenkins: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 2 - /tmp/rhcop/05-08-2020-11-54/charts/jenkins/templates.yaml - Service/jenkins-jnlp: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 3 - /tmp/rhcop/05-08-2020-11-54/charts/jenkins/templates.yaml - DeploymentConfig/jenkins: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 4 - /tmp/rhcop/05-08-2020-11-54/charts/jenkins/templates.yaml - Route/jenkins: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 5 - /tmp/rhcop/05-08-2020-11-54/charts/jenkins/templates.yaml - DeploymentConfig/jenkins: container 'jenkins' does not have an env named 'CONTAINER_MAX_MEMORY' which is used by the Red Hat base images to calculate memory. See: https://docs.openshift.com/container-platform/4.4/nodes/clusters/nodes-cluster-resource-configure.html and https://github.com/jboss-openshift/cct_module/blob/master/jboss/container/java/jvm/bash/artifacts/opt/jboss/container/java/jvm/java-default-options
# not ok 6 - /tmp/rhcop/05-08-2020-11-54/charts/jenkins/templates.yaml - DeploymentConfig/jenkins: container 'jenkins' is from ( ), which is an unknown registry.
# not ok 7 - /tmp/rhcop/05-08-2020-11-54/charts/jenkins/templates.yaml - DeploymentConfig/jenkins: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'app'
# not ok 8 - /tmp/rhcop/05-08-2020-11-54/charts/jenkins/templates.yaml - DeploymentConfig/jenkins: container 'jenkins' has cpu limits (%!d(string=1)). It is not recommended to limit cpu. See: https://www.reddit.com/r/kubernetes/comments/all1vg/on_kubernetes_cpu_limits
# not ok 9 - /tmp/rhcop/05-08-2020-11-54/charts/jenkins/templates.yaml - DeploymentConfig/jenkins: container 'jenkins' has a volumeMount 'jenkins-data' mountPath at '/var/lib/jenkins'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 10 - /tmp/rhcop/05-08-2020-11-54/charts/jenkins/templates.yaml - DeploymentConfig/jenkins: replicas is 1 - expected replicas to be greater than 1 for HA guarantees.
# owncloud
# not ok 1 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - Service/RELEASE-NAME-mariadb: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 2 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - Service/RELEASE-NAME-owncloud: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 3 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - Service/RELEASE-NAME-redis: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 4 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-mariadb: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 5 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-owncloud: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 6 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-redis: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 7 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - Route/RELEASE-NAME-owncloud: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 8 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-mariadb: container 'mariadb' does not have an env named 'CONTAINER_MAX_MEMORY' which is used by the Red Hat base images to calculate memory. See: https://docs.openshift.com/container-platform/4.4/nodes/clusters/nodes-cluster-resource-configure.html and https://github.com/jboss-openshift/cct_module/blob/master/jboss/container/java/jvm/bash/artifacts/opt/jboss/container/java/jvm/java-default-options
# not ok 9 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-mariadb: container 'healthcheck' does not have an env named 'CONTAINER_MAX_MEMORY' which is used by the Red Hat base images to calculate memory. See: https://docs.openshift.com/container-platform/4.4/nodes/clusters/nodes-cluster-resource-configure.html and https://github.com/jboss-openshift/cct_module/blob/master/jboss/container/java/jvm/bash/artifacts/opt/jboss/container/java/jvm/java-default-options
# not ok 10 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-owncloud: container 'owncloud' does not have an env named 'CONTAINER_MAX_MEMORY' which is used by the Red Hat base images to calculate memory. See: https://docs.openshift.com/container-platform/4.4/nodes/clusters/nodes-cluster-resource-configure.html and https://github.com/jboss-openshift/cct_module/blob/master/jboss/container/java/jvm/bash/artifacts/opt/jboss/container/java/jvm/java-default-options
# not ok 11 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-redis: container 'redis' does not have an env named 'CONTAINER_MAX_MEMORY' which is used by the Red Hat base images to calculate memory. See: https://docs.openshift.com/container-platform/4.4/nodes/clusters/nodes-cluster-resource-configure.html and https://github.com/jboss-openshift/cct_module/blob/master/jboss/container/java/jvm/bash/artifacts/opt/jboss/container/java/jvm/java-default-options
# not ok 12 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-redis: container 'healthcheck' does not have an env named 'CONTAINER_MAX_MEMORY' which is used by the Red Hat base images to calculate memory. See: https://docs.openshift.com/container-platform/4.4/nodes/clusters/nodes-cluster-resource-configure.html and https://github.com/jboss-openshift/cct_module/blob/master/jboss/container/java/jvm/bash/artifacts/opt/jboss/container/java/jvm/java-default-options
# not ok 13 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-mariadb: container 'healthcheck' is using the latest tag for its image (docker.io/healthcheck/mysql:latest), which is an anti-pattern.
# not ok 14 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-redis: container 'healthcheck' is using the latest tag for its image (docker.io/healthcheck/redis:latest), which is an anti-pattern.
# not ok 15 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-mariadb: container 'mariadb' is from (docker.io/mariadb:10.4), which is an unknown registry.
# not ok 16 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-mariadb: container 'healthcheck' is from (docker.io/healthcheck/mysql:latest), which is an unknown registry.
# not ok 17 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-owncloud: container 'owncloud' is from ( ), which is an unknown registry.
# not ok 18 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-redis: container 'redis' is from (docker.io/redis:5.0), which is an unknown registry.
# not ok 19 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-redis: container 'healthcheck' is from (docker.io/healthcheck/redis:latest), which is an unknown registry.
# not ok 20 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-mariadb: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'helm.sh/chart'
# not ok 21 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-owncloud: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'deploymentconfig'
# not ok 22 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-owncloud: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'helm.sh/chart'
# not ok 23 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-redis: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'helm.sh/chart'
# not ok 24 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-mariadb: container 'healthcheck' livenessProbe and readinessProbe are equal, which is an anti-pattern.
# not ok 25 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-redis: container 'healthcheck' livenessProbe and readinessProbe are equal, which is an anti-pattern.
# not ok 26 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-mariadb: container 'mariadb' has no livenessProbe. See: https://docs.openshift.com/container-platform/4.4/applications/application-health.html
# not ok 27 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-redis: container 'redis' has no livenessProbe. See: https://docs.openshift.com/container-platform/4.4/applications/application-health.html
# not ok 28 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-mariadb: container 'mariadb' has no readinessProbe. See: https://docs.openshift.com/container-platform/4.4/applications/application-health.html
# not ok 29 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-redis: container 'redis' has no readinessProbe. See: https://docs.openshift.com/container-platform/4.4/applications/application-health.html
# not ok 30 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-mariadb: container 'mariadb' has no memory limits. It is recommended to limit memory, as memory always has a maximum. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers
# not ok 31 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-mariadb: container 'healthcheck' has no memory limits. It is recommended to limit memory, as memory always has a maximum. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers
# not ok 32 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-owncloud: container 'owncloud' has no memory limits. It is recommended to limit memory, as memory always has a maximum. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers
# not ok 33 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-redis: container 'redis' has no memory limits. It is recommended to limit memory, as memory always has a maximum. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers
# not ok 34 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-redis: container 'healthcheck' has no memory limits. It is recommended to limit memory, as memory always has a maximum. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers
# not ok 35 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-mariadb: container 'mariadb' has a volumeMount 'data' mountPath at '/var/lib/mysql'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 36 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-owncloud: container 'owncloud' has a volumeMount 'data' mountPath at '/var/lib/owncloud'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 37 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-redis: container 'redis' has a volumeMount 'data' mountPath at '/data'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 38 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-mariadb: replicas is 1 - expected replicas to be greater than 1 for HA guarantees.
# not ok 39 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-owncloud: replicas is 1 - expected replicas to be greater than 1 for HA guarantees.
# not ok 40 - /tmp/rhcop/05-08-2020-11-54/charts/owncloud/templates.yaml - DeploymentConfig/RELEASE-NAME-redis: replicas is 1 - expected replicas to be greater than 1 for HA guarantees.
# pact-broker
# not ok 1 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - Service/postgresql-pact-broker: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 2 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - Service/pact-broker: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 3 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/pact-broker: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 4 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/postgresql-pact-broker: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 5 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - Route/pact-broker: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 6 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/pact-broker: container 'pact-broker' does not have an env named 'CONTAINER_MAX_MEMORY' which is used by the Red Hat base images to calculate memory. See: https://docs.openshift.com/container-platform/4.4/nodes/clusters/nodes-cluster-resource-configure.html and https://github.com/jboss-openshift/cct_module/blob/master/jboss/container/java/jvm/bash/artifacts/opt/jboss/container/java/jvm/java-default-options
# not ok 7 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/postgresql-pact-broker: container 'postgresql' does not have an env named 'CONTAINER_MAX_MEMORY' which is used by the Red Hat base images to calculate memory. See: https://docs.openshift.com/container-platform/4.4/nodes/clusters/nodes-cluster-resource-configure.html and https://github.com/jboss-openshift/cct_module/blob/master/jboss/container/java/jvm/bash/artifacts/opt/jboss/container/java/jvm/java-default-options
# not ok 8 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/pact-broker: container 'pact-broker' is using the latest tag for its image (pactfoundation/pact-broker:latest), which is an anti-pattern.
# not ok 9 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/pact-broker: container 'pact-broker' is from (pactfoundation/pact-broker:latest), which is an unknown registry.
# not ok 10 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/pact-broker: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'app'
# not ok 11 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/pact-broker: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'deploymentconfig'
# not ok 12 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/postgresql-pact-broker: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'app'
# not ok 13 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/postgresql-pact-broker: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'deploymentconfig'
# not ok 14 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/pact-broker: container 'pact-broker' has no readinessProbe. See: https://docs.openshift.com/container-platform/4.4/applications/application-health.html
# not ok 15 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/pact-broker: container 'pact-broker' has no memory limits. It is recommended to limit memory, as memory always has a maximum. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers
# not ok 16 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/postgresql-pact-broker: container 'postgresql' has no memory limits. It is recommended to limit memory, as memory always has a maximum. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers
# not ok 17 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/pact-broker: container 'pact-broker' has a secret 'pact-broker-secrets' mounted as an environment variable. As secrets are not secret, its not good practice to mount as env vars.
# not ok 18 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/postgresql-pact-broker: container 'postgresql' has a secret 'pact-broker-secrets' mounted as an environment variable. As secrets are not secret, its not good practice to mount as env vars.
# not ok 19 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/postgresql-pact-broker: container 'postgresql' has a volumeMount 'postgresql-pact-broker-data' mountPath at '/var/lib/pgsql/data'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 20 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/pact-broker: has no triggers set. Could you use a k8s native Deployment? See: https://kubernetes.io/docs/concepts/workloads/controllers/deployment
# not ok 21 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/pact-broker: replicas is 1 - expected replicas to be greater than 1 for HA guarantees.
# not ok 22 - /tmp/rhcop/05-08-2020-11-54/charts/pact-broker/templates.yaml - DeploymentConfig/postgresql-pact-broker: replicas is 1 - expected replicas to be greater than 1 for HA guarantees.
# sonarqube
# not ok 1 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Service/postgresql-sonarqube: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 2 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Service/RELEASE-NAME-sonarqube: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 3 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 4 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - DeploymentConfig/postgresql-sonarqube: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 5 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Route/sonarqube: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 6 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: container 'sonarqube' does not have an env named 'CONTAINER_MAX_MEMORY' which is used by the Red Hat base images to calculate memory. See: https://docs.openshift.com/container-platform/4.4/nodes/clusters/nodes-cluster-resource-configure.html and https://github.com/jboss-openshift/cct_module/blob/master/jboss/container/java/jvm/bash/artifacts/opt/jboss/container/java/jvm/java-default-options
# not ok 7 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - DeploymentConfig/postgresql-sonarqube: container 'postgresql' does not have an env named 'CONTAINER_MAX_MEMORY' which is used by the Red Hat base images to calculate memory. See: https://docs.openshift.com/container-platform/4.4/nodes/clusters/nodes-cluster-resource-configure.html and https://github.com/jboss-openshift/cct_module/blob/master/jboss/container/java/jvm/bash/artifacts/opt/jboss/container/java/jvm/java-default-options
# not ok 8 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: container 'sonarqube' is from (sonarqube:8.2-community), which is an unknown registry.
# not ok 9 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'app'
# not ok 10 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'chart'
# not ok 11 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'heritage'
# not ok 12 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'release'
# not ok 13 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - DeploymentConfig/postgresql-sonarqube: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'deploymentconfig'
# not ok 14 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - DeploymentConfig/postgresql-sonarqube: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'app'
# not ok 15 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: container 'sonarqube' has no memory limits. It is recommended to limit memory, as memory always has a maximum. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers
# not ok 16 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - DeploymentConfig/postgresql-sonarqube: container 'postgresql' has no memory limits. It is recommended to limit memory, as memory always has a maximum. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers
# not ok 17 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: container 'sonarqube' has a secret 'postgresql-sonarqube' mounted as an environment variable. As secrets are not secret, its not good practice to mount as env vars.
# not ok 18 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - DeploymentConfig/postgresql-sonarqube: container 'postgresql' has a secret 'postgresql-sonarqube' mounted as an environment variable. As secrets are not secret, its not good practice to mount as env vars.
# not ok 19 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: container 'sonarqube' has a volumeMount 'config' mountPath at '/opt/sonarqube/conf/'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 20 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: container 'sonarqube' has a volumeMount 'sonarqube' mountPath at '/opt/sonarqube/data'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 21 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: container 'sonarqube' has a volumeMount 'sonarqube' mountPath at '/opt/sonarqube/extensions/plugins/tmp'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 22 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: container 'sonarqube' has a volumeMount 'sonarqube' mountPath at '/opt/sonarqube/extensions/downloads'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 23 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: container 'sonarqube' has a volumeMount 'sonarqube' mountPath at '/opt/sonarqube/extensions/plugins'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 24 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: container 'sonarqube' has a volumeMount 'sonarqube' mountPath at '/opt/sonarqube/temp'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 25 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: container 'sonarqube' has a volumeMount 'sonarqube' mountPath at '/opt/sonarqube/logs'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 26 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: container 'sonarqube' has a volumeMount 'tmp-dir' mountPath at '/tmp'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 27 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: container 'sonarqube' has a volumeMount 'copy-plugins' mountPath at '/tmp/scripts'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 28 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - DeploymentConfig/postgresql-sonarqube: container 'postgresql' has a volumeMount 'postgresql-sonarqube' mountPath at '/var/lib/pgsql/data'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 29 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: volume 'install-plugins' does not have a volumeMount in any of the containers.
# not ok 30 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - Deployment/RELEASE-NAME-sonarqube: replicas is 1 - expected replicas to be greater than 1 for HA guarantees.
# not ok 31 - /tmp/rhcop/05-08-2020-11-54/charts/sonarqube/templates.yaml - DeploymentConfig/postgresql-sonarqube: replicas is 1 - expected replicas to be greater than 1 for HA guarantees.
# sonatype-nexus
# not ok 1 - /tmp/rhcop/05-08-2020-11-54/charts/sonatype-nexus/templates.yaml - Service/sonatype-nexus-service: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 2 - /tmp/rhcop/05-08-2020-11-54/charts/sonatype-nexus/templates.yaml - Deployment/RELEASE-NAME-sonatype-nexus: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 3 - /tmp/rhcop/05-08-2020-11-54/charts/sonatype-nexus/templates.yaml - Route/nexus: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 4 - /tmp/rhcop/05-08-2020-11-54/charts/sonatype-nexus/templates.yaml - Deployment/RELEASE-NAME-sonatype-nexus: container 'nexus' does not have an env named 'CONTAINER_MAX_MEMORY' which is used by the Red Hat base images to calculate memory. See: https://docs.openshift.com/container-platform/4.4/nodes/clusters/nodes-cluster-resource-configure.html and https://github.com/jboss-openshift/cct_module/blob/master/jboss/container/java/jvm/bash/artifacts/opt/jboss/container/java/jvm/java-default-options
# not ok 5 - /tmp/rhcop/05-08-2020-11-54/charts/sonatype-nexus/templates.yaml - Deployment/RELEASE-NAME-sonatype-nexus: container 'nexus' is from (registry.connect.redhat.com/sonatype/nexus-repository-manager:3.24.0-ubi-1), which is an unknown registry.
# not ok 6 - /tmp/rhcop/05-08-2020-11-54/charts/sonatype-nexus/templates.yaml - Deployment/RELEASE-NAME-sonatype-nexus: container 'nexus' contains -Xmx in either, command, args or env. Instead, it is suggested you use the downward API to set the env 'CONTAINER_MAX_MEMORY'
# not ok 7 - /tmp/rhcop/05-08-2020-11-54/charts/sonatype-nexus/templates.yaml - Deployment/RELEASE-NAME-sonatype-nexus: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'heritage'
# not ok 8 - /tmp/rhcop/05-08-2020-11-54/charts/sonatype-nexus/templates.yaml - Deployment/RELEASE-NAME-sonatype-nexus: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'release'
# not ok 9 - /tmp/rhcop/05-08-2020-11-54/charts/sonatype-nexus/templates.yaml - Deployment/RELEASE-NAME-sonatype-nexus: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'app'
# not ok 10 - /tmp/rhcop/05-08-2020-11-54/charts/sonatype-nexus/templates.yaml - Deployment/RELEASE-NAME-sonatype-nexus: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'chart'
# not ok 11 - /tmp/rhcop/05-08-2020-11-54/charts/sonatype-nexus/templates.yaml - Deployment/RELEASE-NAME-sonatype-nexus: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'fullname'
# not ok 12 - /tmp/rhcop/05-08-2020-11-54/charts/sonatype-nexus/templates.yaml - Deployment/RELEASE-NAME-sonatype-nexus: container 'nexus' livenessProbe and readinessProbe are equal, which is an anti-pattern.
# not ok 13 - /tmp/rhcop/05-08-2020-11-54/charts/sonatype-nexus/templates.yaml - Deployment/RELEASE-NAME-sonatype-nexus: container 'nexus' has no memory limits. It is recommended to limit memory, as memory always has a maximum. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers
# not ok 14 - /tmp/rhcop/05-08-2020-11-54/charts/sonatype-nexus/templates.yaml - Deployment/RELEASE-NAME-sonatype-nexus: container 'nexus' has a volumeMount 'RELEASE-NAME-sonatype-nexus-data' mountPath at '/nexus-data'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 15 - /tmp/rhcop/05-08-2020-11-54/charts/sonatype-nexus/templates.yaml - Deployment/RELEASE-NAME-sonatype-nexus: container 'nexus' has a volumeMount 'RELEASE-NAME-sonatype-nexus-backup' mountPath at '/nexus-data/backup'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 16 - /tmp/rhcop/05-08-2020-11-54/charts/sonatype-nexus/templates.yaml - Deployment/RELEASE-NAME-sonatype-nexus: replicas is 1 - expected replicas to be greater than 1 for HA guarantees.
# static-site
# not ok 1 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Service/static-site-RELEASE-NAME: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 2 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: does not contain all the expected k8s labels in 'metadata.labels'. See: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels
# not ok 3 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: container 'nginx' does not have an env named 'CONTAINER_MAX_MEMORY' which is used by the Red Hat base images to calculate memory. See: https://docs.openshift.com/container-platform/4.4/nodes/clusters/nodes-cluster-resource-configure.html and https://github.com/jboss-openshift/cct_module/blob/master/jboss/container/java/jvm/bash/artifacts/opt/jboss/container/java/jvm/java-default-options
# not ok 4 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: container 'git' does not have an env named 'CONTAINER_MAX_MEMORY' which is used by the Red Hat base images to calculate memory. See: https://docs.openshift.com/container-platform/4.4/nodes/clusters/nodes-cluster-resource-configure.html and https://github.com/jboss-openshift/cct_module/blob/master/jboss/container/java/jvm/bash/artifacts/opt/jboss/container/java/jvm/java-default-options
# not ok 5 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: container 'nginx' is from (nginx:1.17.9-alpine), which is an unknown registry.
# not ok 6 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: container 'git' is from (jijiechen/alpine-curl-git:v2.24.1), which is an unknown registry.
# not ok 7 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'app'
# not ok 8 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: has a label key which did not start with 'app.kubernetes.io/' or 'redhat-cop.github.com/'. Found 'site'
# not ok 9 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: container 'git' has no livenessProbe. See: https://docs.openshift.com/container-platform/4.4/applications/application-health.html
# not ok 10 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: container 'git' has no readinessProbe. See: https://docs.openshift.com/container-platform/4.4/applications/application-health.html
# not ok 11 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: container 'nginx' has cpu limits (%!d(string=200m)). It is not recommended to limit cpu. See: https://www.reddit.com/r/kubernetes/comments/all1vg/on_kubernetes_cpu_limits
# not ok 12 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: container 'git' has no memory limits. It is recommended to limit memory, as memory always has a maximum. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers
# not ok 13 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: container 'nginx' has a volumeMount 'website' mountPath at '/usr/share/nginx/html'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 14 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: container 'nginx' has a volumeMount 'config' mountPath at '/etc/nginx/nginx.conf'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 15 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: container 'nginx' has a volumeMount 'config' mountPath at '/etc/nginx/conf.d/default.conf'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 16 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: container 'git' has a volumeMount 'website' mountPath at '/website'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 17 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: container 'git' has a volumeMount 'source' mountPath at '/source'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 18 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: container 'git' has a volumeMount 'config' mountPath at '/git/clone.sh'. A good practice is to use consistent mount paths, such as: /var/run/{organization}/{mount} - i.e.: /var/run/io.redhat-cop/my-secret
# not ok 19 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: replicas is 0 - expected replicas to be greater than 1 for HA guarantees.
# not ok 20 - /tmp/rhcop/05-08-2020-11-54/charts/static-site/templates.yaml - Deployment/static-site-RELEASE-NAME: replicas is 0 - expected an odd number for HA guarantees.