redhat-cop / helm-charts

Helm Charts Repository

⚓️ Red Hat Communities of Practice Helm Charts

A collection of Helm Charts to that are not available in any upstream location or customised to the point it does not make sense to support up stream chart development.

For charts we know work on OpenShift but do not belong here, check out the list of Charts we've used for some ideas

This library is used to support Open Innovation Labs Ubiquitous Journey Project

Additional charts for managing an OpenShift cluster can be found in redhat-cop/openshift-management

🧰 Add this Helm Repo to your local 🧰

helm repo add redhat-cop https://redhat-cop.github.io/helm-charts

🏃‍♀️💨 How do I run a chart?

Login to your cluster and into your destination project. To install any given Chart using the default values just run:

helm install $NAME redhat-cop/$CHART_NAME
eg:
helm install my-jenkins redhat-cop/jenkins

Where:

• $NAME - is the name you want to give the installed Helm App
• $CHART_NAME - name of the chart found in charts directory

🏃‍♂️💨Customisation to a chart prior to install

For each chart, navigate to the root of it for the readme and default values. To over ride them, you could create your own my-values.yaml and make your changes there before installing

helm install $NAME -f my-values.yaml redhat-cop/$CHART_NAME
eg:
helm install my-jenkins -f my-values.yaml redhat-cop/jenkins

🏃‍♂️💨 Chart linting

Before adding a chart to this repo, make sure there is no linting issues, otherwise the PR actions will fail. We use both the integrated helm lint command and the chart testing tool.

helm lint charts/jenkins
ct lint charts/jenkins

👩‍🏫 Chart README Files

For more info on each chart checkout these!

• ansible-automation-platform
• argocd-operator
• bootstrap-project
• dev-ex-dashboard
• etherpad
• gitops-operator
• helper-console-links
• helper-sealed-secrets
• jenkins
• kopf
• network-policy
• openshift-logforwarding-splunk
• operatorhub
• operators-installer
• owncloud
• pact-broker
• ploigos
• sonarqube
• sonatype-nexus
• stackrox
• static-site
• tekton-demo
• operators-installer

helm-charts's Issues

Write docs

Each chart should probs have some docs. Highlighting the over rides etc

bump helm charts via renovate

linting fails when renovate opens a PR against a chart. need to bump somehow

operatorhub: operatorgroup.create docs slightly miss-leading

operatorhub chart supports: operatorgroup.create in the docs;

• https://github.com/rht-labs/helm-charts/tree/master/charts/operatorhub#configuration

Since the example is true, it's inferred that the below should not create the operator group:

operatorgroup:
        create: false

But the code just checks for the existence of the 'operatorgroup', so it doesn't matter what create is set to.

• https://github.com/rht-labs/helm-charts/blob/master/charts/operatorhub/templates/operatorgroup.yaml#L3

the wording of the docs just needs tweaking to make this clear.

CC @springdo @ckavili

Ploigos gets stuck on cluster-check

I've just tried to install ploigos, but it gets stuck on the cluster-check (CRD never gets created)

cd ploigos
export project_name="ploigos-$(date +'%d%m%Y')"
oc new-project ${project_name}
helm install ploigos -f values.yaml --set-string operator.namespaces[0].name=${project_name} .

@eformat ; any ideas?

s/master/main/g 🥢

run release on pr

is there an approach we can take to run the release workflow on PR? I am thinking about where PRs are raised which change this workflow. there isn't anything in the PR to say it works or not, it's down to the reviewer to check the workflow on the PR raisers repo (i.e.: upstream)

wondering if we could do a draft release? or the version based on the PR number? i.e.: {chart}-PR{pr-number}

thoughts? @ckavili @springdo @eformat @tylerauerbeck

How to deploy gitops operator on a different namespace instead of labs-ci-cd

We were trying to deploy gitops operator using helm chart using terraform's helm_release
by default its using labs-ci-cd as a namespace.

The requirement was to deploy this on another namespace instead of labs-ci-cd

can someone help us on this

@garethahealy @ckavili
Sorry. Not sure whom to ask so creating a issue here.

Plugins.txt

Hi,

Is there a way that I can add a plugins.txt file with a team needed plugins somewhere?

🦅 Migrate helm templates from UJ to here

• ArgoCD Operator deploy templates living in uj should live here

Switch CR_TOKEN to the ci bot

Currently, CR_TOKEN is @springdo - probably a good idea to switch it to @redhat-cop-ci-bot

chart releaser fails during concurrent runs

if you accidentally merge two PR's before the chart release action has finished, the index.yaml file is overwritten instead of appended to. this sort of thing happens and your chart (ipa in this case) is not released.

we need to fix up the gh-actions on this

Jenkins Deployment Memory Limit always the same as Request Memory

If the deployment.limits.memory_limit value is changed it isn't set in the resulting DeploymentConfig.
It is always set to the deployment.limits.memory_request value.

bootstrap-project; unable to provide no bindings

When using the bootstrap-project, I was hoping I could use a simple values.yml like:

enabled: true
namespaces:
- name: bob

but this outputs:

---
# Source: cluster-bootstrap/charts/bootstrap-project/templates/namespace.yaml
apiVersion: v1
kind: Namespace
metadata:
  name: "bob"
---
# Source: cluster-bootstrap/charts/bootstrap-project/templates/serviceaccount.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  name: dummy-sa
  namespace: "labs-ci-cd"
---
# Source: cluster-bootstrap/charts/bootstrap-project/templates/bindings.yaml
apiVersion: v1
kind: List
metadata:
  annotations:
    # This is what defines this resource as a hook. Without this line, the
    # job is considered part of the release.
    "helm.sh/hook": post-install
items:

I'd of expected it not to create a serviceaccount or list of bindings.

CC @springdo ; re: gchat

template vs install vs argocd

what is the expectation from this repo around $subject? i.e.: do we expect all charts can be installed by helm template and run on argocd?

I presume that's not 100% true, as I know some charts use hooks that template/argo don't support.

Q: do we expect all charts should run on argo without issue?
Q: should we standardise in a certain way? template vs install
Q: or do we just need to call out in the readme's what is supported/not?

thoughts @ckavili @springdo @eformat

Cant deploy sonarqube.

It seems the sonarqube deployment and the postgresql dc are using the same Claim volume name.... and also that there isnt a PVC for postgresql...

Etherpad Fixed Version

It is not possible to change the name as well as the tag of the image.

The image name and tag should be configurable.

PR: Follows shortly

Remove sealed-secret chart when upstream changes merged.

helm/charts#22722

add helm tests to charts

based on conversations (#137), we should add more tests to the charts.

Charts using the removed APIs in k8s 1.22 requires changes🧩

Deprecated APIs extensions/v1beta1 and networking.k8s.io/v1beta1 needs to be migrated to networking.k8s.io/v1 in below charts.

• sonarqube chart
• etherpad chart
• nexus chart

argocd testing

i pushed the prow.sh, which can be used locally but is hoped would be used by prow CI in the future (TBD). but do we need another test scenario to check the charts work in argocd?

• https://github.com/redhat-cop/helm-charts/blob/master/_test/prow.sh

i.e.: a script that creates all the charts in an argocd instance and checks they've all run successfully.

thoughts @ckavili @springdo @eformat ?

sonar.properties not being reflected

The chart correctly initializes the container (downloads and installs plugins and populated the conf/sonar.properties file, however, the properties set are not being reflected. Is there a command that I need to run to make the changes stick?

I tested this with SMTP settings and the server did not pick them up. These are core settings in SQ, and there are a lot of settings that I need to set for plugins such as the OpenShift authentication plugin.

Manage Operators console plugins with operators-install chart

operators-installer helm chart is great, but IMHO there is one missing feature regarding installing operators via OLM. Managing operator console plugins.

When installing operators via OLM using OpenShift UI, most of the times the operator console plugin is enabled by default, and taken care by OLM itself. Also most operators (at least Red Hat operators) come with their own console plugins.

When installing operators using GitOps, we are missing this functionality. I tried a simple approach here, and it worked. It is not idempotent at the moment, it will only take afew lines.

Also now that ArgoCD supports (since v2.10) a PostDelete hook, we could use that to do the cleanup of the plugin after uninstalling the operator.

@itewk leaving this here in case I have time to do a PR in the future.

attach intoto to release

With #425 merged, intoto files are generated and attached to sigstore public infra, see: https://search.sigstore.dev/?uuid=24296fb24b8ad77a84d44942175fed2bbdad845e4ade10ae078ed53d76b556e132cd6bbac93e8bf4.

the github action can also attach the intoto doc to a release as a release artifact, see: policy.tar.intoto.jsonl

the reason it doesn't, is because CT does the release so the action doesn't know what release its working against. would be nice if we can figure out a way to get this working

argocd using cop image

Any reason to use the CoP image?

• https://github.com/rht-labs/helm-charts/blob/master/charts/argocd-operator/templates/ArgoCD.yaml#L14

cant the chart just use dex v2.22.0?

CC @eformat @springdo

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

These problems occurred while renovating this repository. View logs.

• WARN: Package lookup failures

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• Update docker.io/mariadb Docker tag to v11.5
• Update sonarqube Docker tag to v10.6.0

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• Update dependency helm/helm to v3.15.4
• Update github/codeql-action action to v3.26.5
• Update dependency kubernetes-sigs/kind to v0.24.0
• 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• Update alpine/git:v2.43.0 Docker digest to 76fdb72
• Update docker.io/mariadb:11.3 Docker digest to e101f9d
• Update docker.io/redis:7.2 Docker digest to f65071a
• Update registry.access.redhat.com/ubi8/ubi:latest Docker digest to d5e2d1d
• Update registry.redhat.io/openshift4/ose-cli:latest Docker digest to dbb4181
• Update registry.redhat.io/rhel8/buildah Docker digest to 2318962
• Update registry.redhat.io/ubi8/ubi:latest Docker digest to d5e2d1d
• Update sonarqube:10.5.1-community Docker digest to b3c2031
• Update alpine/git Docker tag to v2.45.2
• Update docker.io/redis Docker tag to v7.4

---

Warning

Renovate failed to look up the following dependencies: Failed to look up docker package registry.redhat.io/openshift4/ose-cli.

Files affected: charts/operators-installer/values.yaml

---

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency python/cpython to v3.12.5

Detected dependencies

ansible

charts/tekton-demo/templates/tasks/conditions.yaml

• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7
• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7

charts/tekton-demo/templates/tasks/task-apply.yaml

• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7

charts/tekton-demo/templates/tasks/task-build.yaml

• registry.redhat.io/rhel8/buildah sha256:de42c2158dceaa97f70cd6ce92cd7087538c5d2caad29da4b8ca34a0e8b041a0
• registry.redhat.io/rhel8/buildah sha256:de42c2158dceaa97f70cd6ce92cd7087538c5d2caad29da4b8ca34a0e8b041a0

charts/tekton-demo/templates/tasks/task-deploy.yaml

• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7
• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7
• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7
• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7
• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7
• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7
• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7
• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7

charts/tekton-demo/templates/tasks/task-docs.yaml

• registry.redhat.io/rhel8/buildah sha256:de42c2158dceaa97f70cd6ce92cd7087538c5d2caad29da4b8ca34a0e8b041a0
• registry.redhat.io/rhel8/buildah sha256:de42c2158dceaa97f70cd6ce92cd7087538c5d2caad29da4b8ca34a0e8b041a0
• registry.redhat.io/rhel8/buildah sha256:de42c2158dceaa97f70cd6ce92cd7087538c5d2caad29da4b8ca34a0e8b041a0

charts/tekton-demo/templates/tasks/task-finally.yaml

• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6

charts/tekton-demo/templates/tasks/task-git-clone.yaml

• gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/git-init v0.45.0@sha256:8ab0f58d8381b0b71f5b2bae1f63522989d739e3154d8cab1bacfa0ef5317214
• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7
• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6

charts/tekton-demo/templates/tasks/task-github-pull-request.yaml

• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6

charts/tekton-demo/templates/tasks/task-github.yaml

• registry.access.redhat.com/ubi8/ubi latest@sha256:83068ea81dd02717b8e39b55cdeb2c1b2c9a3db260f01381b991755d44b15073

charts/tekton-demo/templates/tasks/task-helm.yaml

• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6
• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6

charts/tekton-demo/templates/tasks/task-prepare.yaml

• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6
• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6
• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6

charts/tekton-demo/templates/tasks/task-promote.yaml

• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6
• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6
• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7
• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7
• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7
• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7
• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7
• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7
• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7
• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7
• registry.redhat.io/ubi8/ubi latest@sha256:edc34f89cf9c818c2fb28b8ea1780f384db563ce4293dc0ab8e73ec01791e5af

charts/tekton-demo/templates/tasks/task-standards.yaml

• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6
• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6
• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6
• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6
• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6
• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6

charts/tekton-demo/templates/tasks/task-status.yaml

• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7
• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6

charts/tekton-demo/templates/tasks/task-tag.yaml

• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6

charts/tekton-demo/templates/tasks/task-test-integration.yaml

• registry.redhat.io/rhel8/nodejs-12 sha256:3c7f0b36e4313819009df28c4b666320e0cff45041ccbc3861327054f9e1d1f6
• registry.redhat.io/ubi8/ubi latest@sha256:edc34f89cf9c818c2fb28b8ea1780f384db563ce4293dc0ab8e73ec01791e5af

charts/tekton-demo/templates/tasks/task-test-performance.yaml

• registry.redhat.io/openshift4/ose-cli latest@sha256:5690a3e95f381102a9cbcf13c39c538c7d55c7ba9d4a494e2d22542b703601c7

dockerfile

charts/static-site/alpine-curl-git.Dockerfile

• alpine/git v2.43.0@sha256:5be7ad4ab6bbd7f24a66224c814aa030c2abad186d839c8b6c1210585d96e25c

github-actions

.github/workflows/conftest.yaml

• actions/checkout v4@692973e3d937129bcbf40652eb9f2f61becf3332
• redhat-cop/github-actions v4.3@1a584131f8a335296e866d1fb0988870ca83aefb

.github/workflows/install-integration-tests-operators-installer.yaml

• actions/checkout v4@692973e3d937129bcbf40652eb9f2f61becf3332
• azure/setup-helm v4@fe7b79cd5ee1e45176fcad797de68ecaf3ca4814
• actions/setup-python v5@39cd14951b08e74b54015e9e001cdefcf80e669f
• helm/kind-action v1.10.0@0025e74a8c7512023d06dc019c617aa3cf561fde

.github/workflows/install-unit-test.yaml

• actions/checkout v4@692973e3d937129bcbf40652eb9f2f61becf3332
• azure/setup-helm v4@fe7b79cd5ee1e45176fcad797de68ecaf3ca4814
• actions/setup-python v5@39cd14951b08e74b54015e9e001cdefcf80e669f
• helm/chart-testing-action v2.6.1@e6669bcd63d7cb57cb4380c33043eebe5d111992
• helm/kind-action v1.10.0@0025e74a8c7512023d06dc019c617aa3cf561fde

.github/workflows/lint-test.yaml

• actions/checkout v4@692973e3d937129bcbf40652eb9f2f61becf3332
• azure/setup-helm v4@fe7b79cd5ee1e45176fcad797de68ecaf3ca4814
• actions/setup-python v5@39cd14951b08e74b54015e9e001cdefcf80e669f
• helm/chart-testing-action v2.6.1@e6669bcd63d7cb57cb4380c33043eebe5d111992

.github/workflows/release.yaml

• actions/checkout v4@692973e3d937129bcbf40652eb9f2f61becf3332
• azure/setup-helm v4.2.0@fe7b79cd5ee1e45176fcad797de68ecaf3ca4814
• helm/chart-releaser-action v1.6.0@a917fd15b20e8b64b94d9158ad54cd6345335584
• sigstore/cosign-installer v3@59acb6260d9c0ba8f4a2f9d9b48431a222b68e20
• slsa-framework/slsa-github-generator v2.0.0

.github/workflows/scorecard.yml

• actions/checkout v4.1.7@692973e3d937129bcbf40652eb9f2f61becf3332
• ossf/scorecard-action v2.4.0@62b2cac7ed8198b15735ed49ab1e5cf35480ba46
• actions/upload-artifact v4.3.6@834a144ee995460fba8ed112a2fc961b36a5ec5a
• github/codeql-action v3.26.0@eb055d739abdc2e8de2e5f4ba1a8b246daa779aa

helm-values

charts/etherpad/values.yaml

• etherpad undefined

charts/ipa/values.yaml

charts/openshift-logforwarding-splunk/values.yaml

• registry.redhat.io/openshift4/ose-logging-fluentd v4.6@sha256:858cbcf1bb6f7e5641bd0a8914b92237190037cefdffa2c069b0ddc9a6c5ae9d

charts/operators-installer/values.yaml

• registry.redhat.io/openshift4/ose-cli v4.15@sha256:3f2123f42ae7358e1fece41d461bf331f144480da8b7711b9a93aca150f33f3f

charts/owncloud/values.yaml

• docker.io/redis 7.2@sha256:f14f42fc7e824b93c0e2fe3cdf42f68197ee0311c3d2e0235be37480b2e208e6
• docker.io/healthcheck/redis latest@sha256:06127d640e5c092f4707e3506e3a80c0361225b8da735b54d66e162a79d1fa38
• docker.io/mariadb 11.3@sha256:78d0c3b8c39b47e91cc32df64ef1e26f797b54b1dd762c850e7350095ed4715f
• docker.io/healthcheck/mysql latest@sha256:b7a7b38485b0d93bfc12a42f870dcf8b27c9ba854c9a28d4d26ed941a113ee20

charts/sonarqube/values.yaml

• sonarqube 10.5.1-community@sha256:802aa4f65983d43e40f230db9bfcc7fa2b796561fb40f018e9e23516640e7553

helmv3

charts/ansible-automation-platform/Chart.yaml

• operatorhub 0.0.10

charts/ipa/Chart.yaml

• cronjob-ldap-group-sync 0.0.2

regex

.github/workflows/install-integration-tests-operators-installer.yaml

• helm/helm v3.15.3
• python/cpython v3.12.4
• kubernetes-sigs/kind v0.23.0
• operator-framework/operator-lifecycle-manager v0.28.0

.github/workflows/install-unit-test.yaml

• helm/helm v3.15.3
• python/cpython v3.12.4
• kubernetes-sigs/kind v0.23.0
• operator-framework/operator-lifecycle-manager v0.28.0

.github/workflows/lint-test.yaml

• helm/helm v3.15.3
• python/cpython v3.12.4
• pybump 1.12.4

.github/workflows/release.yaml

• helm/helm v3.15.3

---

• Check this box to trigger a request for Renovate to run again on this repository

ArgoCD HA Redis SA has too wide permissions.

I believe this does not need to be a ClusterRole, plus the SA is named: argocd-argocd-reids-ha.

helm-charts/charts/argocd-operator/templates/anyuid-scc.yaml

Line 18 in b008377

kind: ClusterRoleBinding

openshift-logforwarding-splunk fluentd image deprecated

openshift-logforwarding-splunk uses the below image:

• https://github.com/redhat-cop/helm-charts/blob/main/charts/openshift-logforwarding-splunk/values.yaml#L48

which is now deprecated:

• https://catalog.redhat.com/software/containers/openshift4/ose-logging-fluentd/5cd9744edd19c778293af093?container-tabs=overview&architecture=amd64&image=63614e4872f7b44d16bc9b55

@sabre1041 ; do you know if anyone is still using this? can the image ref be simply switched out to:

• https://catalog.redhat.com/software/containers/openshift-logging/fluentd-rhel9/6447991e7876547f4e556a0a?architecture=amd64&image=653accdffb854b56a290d80e&container-tabs=gti

🥴 mvn-slave using eformat fork

Issue to track when eformat's fork of the jenkins slave can be resolved. #46

How to deploy ansible-automation-platform using helm chat

We were trying to deploy gitops operator using helm chart using terraform's helm_release
Getting this error.
YAML parse error on ansible-automation-platform/templates/privileged-scc.yaml: error converting YAML to JSON: yaml: line 3: did not find expected key

can someone help us on this

@garethahealy @ckavili @eformat
Sorry. Not sure whom to ask so creating a issue here.

How to deploy ansible-automation-platform without creating local postgres pod

Hi,

We were trying to deploy AAP operator using helm chart. We were planning to deploy operator integrating with Azure postgres, But locally postgres pod was getting created.

We need to stop the pod getting created.

can someone help us on this

@garethahealy @ckavili @eformat @schen1
Sorry. Not sure whom to ask so creating a issue here.

argocd-operator always creates an operatorgroup

If an operator group already exists in a project, creating another one causes conflicts/issues with the OLM.

CC @springdo

ClusterServiceVersion is not deleted after helm uninstall action

After creating a operator subscription with the helm operatorhub chart, it creates the subs successfully:

For example lets install the amq-streams operator with the operatorhub chart:

helm install rht-labs/operatorhub --generate-name --set operators[0].name=amq-streams,operators[0].namespace=rht-labs-trials,operators[0].subscription.operatorName=amq-streams,operators[0].subscription.channel=stable,operators[0].subscription.csv=amqstreams.v1.4.0,operators[0].operatorgroup.create=true

It creates the helm instance successfully:

NAME: operatorhub-0-1586213116
LAST DEPLOYED: Tue Apr 7 01:45:18 2020
NAMESPACE: rht-labs-trials
STATUS: deployed
REVISION: 1
TEST SUITE: None

And installs the operator:

But when trying to uninstall the chart, it does remove the resources that are created by itself but not the ClusterServiceVersion which is created automatically while subscribing:

move stack rox chart to here

@eformat - do you wanna pop this chart in this repo https://github.com/rht-labs/stackrox-chart?

conftest --all-namespace violations

# 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.

The images on the GitHub pages site is offensive and unprofessional

'nuff said.

CI for this repo does not support Shift Objects

currently the gh actions uses this repo which uses a kind k8s cluster to install and verify the k8s objects. It barfs at OCP specific ones such as BuildConfig etc.

https://github.com/helm/chart-testing-action

Perhaps we could create our own test bed in s43 or something like that to create a proj, apply and see if there are errors. then delete when done

Unable to access to ArgoCD UI in Firefox: SEC_ERROR_BAD_DER

Deploying ArgoCD following the instructions in README.md with default values works smothly, however it is not possible to access to the UI using Firefox.

The following messages are showed in the browser without any capability to navigate:

Secure Connection Failed

An error occurred during a connection to argocd-server-labs-ci-cd.apps.cluster-e381.e381.sandbox1862.opentlc.com. security library: improperly formatted DER-encoded message.

Error code: SEC_ERROR_BAD_DER

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
    Please contact the website owners to inform them of this problem.

The same route works successfully in Chrome.

Environment:

• OpenShift 4.8
• ArgoCD Operator 0.0.15
• Firefox 94.0 (64-bit)
• Fedora 34

PS: Open this issue initialy here, as I am not sure if the issue is related with the Helm Chart, OpenShift 4.8 (provided by RHPDS) or finally it is an issue of Argo CD.

How install your nexus chart for kubernetes?

Hello! I try install nexus chat to kubernetes and get error

helm repo add redhat-cop https://redhat-cop.github.io/helm-charts
helm repo update
helm install  nexus redhat-cop/sonatype-nexus

Get error

Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Route" in version "route.openshift.io/v1"

Helm3 and App Version

Our appVersion is not set correct in our charts. It should be set to the version of the deployed app. We should also bump all our charts to helm v3

SonarQube Plugin Install

I'm having issues getting any language template plugins installed. I've got some entries in the values.yaml for plugins.install. I see them get put into the sonarqube-install-plugins ConfigMap but nothing is installed once SonarQube comes up. I've looked in the /opt/sonarqube/extensions/plugins folder and nothing shows up there. Any thoughts on what I might be missing?

[nice to have] - add icons to our charts

OpenShift 4.6 includes the ability to add helm repos as catalogs in the dev view. We should add icons to the helm charts so they look nice in OCP Land and don't just have the generic Helm Logo.

FYI - @ckavili / @mvmaestri