sonatype/helm3-charts

Helm3 charts for Nexus IQ

helm3-charts's Issues

Chart fails when `nexus.extraLabels` is used

Adding a nexus.extraLabels mapping causes templating to fail with the following message:

Error: YAML parse error on nexus-repository-manager/templates/deployment.yaml: error converting YAML to JSON: yaml: line 11: mapping values are not allowed in this context

Looking at the output with --debug, it appears the the first entry in the extraLabels map is indented too far, and this is causing the problem.

The template files seem to use the syntax:

  {{- if .Values.nexus.extraLabels }}
    {{- with .Values.nexus.extraLabels }}
      {{ toYaml . | indent 4 }}
    {{- end }}
  {{- end }}

I believe switching from indent to nindent should fix the issue.

Http to Https

How to be secure the url , means like connection is secure ,when we hit in browser, It has to show like a secure know.
I am getting the not secure can you please help me in this it will helpful a lot for me

[sonatype/nexus-repository-manager] warning message when install

Hi,

as you know, there is warning message.
And please update NOTES message.

One more thing, please make helm chart is first-class deployment method of nexus, support fully by sonatype.
I think this chart is still not active than oteemo's actually.

$ k create ns nexus-test
namespace/nexus-test created
$ helm install -n nexus-test nexus-test -f nexus-test-values.yaml sonatype/nexus-repository-manager
coalesce.go:199: warning: destination for data is a table. Ignoring non-table value []
NAME: nexus-test
LAST DEPLOYED: Tue Dec  1 15:29:36 2020
NAMESPACE: nexus-test
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
1. Get the application URL by running these commands:

Upgrade nexus-repository-manager image to 3.31.0+

Known CVE in 3.30.1, resolved in 3.31.0+

https://help.sonatype.com/repomanager3/release-notes#ReleaseNotes-NexusRepositoryManager3.31.0

Conflicting README Information Regarding Use of StatefulSets

It's listed in this README that in order to use a persistent volume to enable statefulSet instead of using the default deployment. However, the values.yaml says it's not supported, and there's no templates relating to a statefulSet.

How are you supposed to guarantee a pod is reconnected to its PVC without a statefulSet in the event that it's recreated?

Unable to execute HTTP request: Timeout waiting for connection from pool

Hello team,

We are running OSS Nexus Sonatype on helm kubernetes and, from time to time, we are receiving the following error: Unable to execute HTTP request: Timeout waiting for connection from pool
And we only need to restart the pod.

Could you, please, tell us what can be the problem here?
nexsus-logs.txt

Attached you can find all the logs. We also increased the Java memory for the process, but no luck.

Thank you,
-Ionut

Accessing Nexus repository manager password in a kubernetes pod

I have installed Sonatype nexus repository manager in my Kubernetes Cluster using the helm chart,

I am using Kyma installation.

Nexus repository manager got installed properly and i can access the application.

But it seems the login password file is in a pv volume claim /nexus-data attached in the pod.

Now whenever i am trying to access the pod with kubectl exec command

kubectl exec -i -t $POD_NAME -n dev -- /bin/sh
I am getting the following error

OCI runtime exec failed: exec failed: container_linux.go:367: starting container process caused: exec: "/bin/sh": stat /bin/sh: no such file or directory: unknown
I understand that this issue is because of the image does not offer shell functionality. Is there any other way i can access the password file present in the pvc ?

Does this work for nexus3 pro ?

Does this work for nexus3 pro ?

[nexus-repository-manager] Bug in imagePullSecret

Hi,

there's imagePullSecrets

helm3-charts/charts/nexus-repository-manager/values.yaml

Line 70 in 4e3d346

imagePullSecrets: []

But in template,
used nexus.imagePullSecret,

helm3-charts/charts/nexus-repository-manager/templates/deployment.yaml

Lines 51 to 54 in 4e3d346

	{{- if .Values.nexus.imagePullSecret }}
	imagePullSecrets:
	{{- toYaml . | nindent 8 }}
	{{- end }}

and please remove image-pull-secret.yaml file, you don't need to create secret for user.

Most of usecase, I think below syntax.

imagePullSecrets:
  - name: secret-name

Support to block /swagger-ui

Hi,

This is basically a feature request. It would be nice to have support in the ingress template to block /swagger-ui. Other people have asked for it: https://community.sonatype.com/t/is-it-possible-to-protect-or-disable-the-swagger-ui/6077

For AWS load balancer controller a flag in values file to block swagger-ui can trigger a conditional block that will add an additional rule:

- host: {{ .Values.ingress.hostRepo }}
    http:
      paths:
      - backend:
          serviceName: response-404
          servicePort: use-annotation
        path: /swagger-ui*

And the annotation to the ingress:

alb.ingress.kubernetes.io/actions.response-404: >
      {"Type":"fixed-response","FixedResponseConfig":{"ContentType":"text/plain","StatusCode":"404","MessageBody":"404 error text"}}

Suggestions from afar

Just wanted to say it is awesome to see you taking over the helm chart. Just a tip for help with the automation of releases: https://github.com/helm/charts-repo-actions-demo.

Automatic license configuration is not working

The licenseFile seems to be in the wrong place here:

helm3-charts/nexus-iq/values.yaml

Line 20 in 1c0a876

# licenseFile: /etc/nexus-iq-license/license_lic

When placed under configYaml resource the same, I was able to install the license automatically:
https://github.com/sonatype/helm3-charts/blob/master/nexus-iq/values.yaml#L105

Use existing secrets

I use helmfile to deploy this chart, and need to be able to do this without checking in the licence and other sensitive information. Being able to use an existing secret for the licence and config.yml would help very much.

27.0.2 not mounting nexus-data PVC

Hi,

I've noticed this commit 2175409#diff-bfac4247543c05f946d981c211baba2dL106 (in the most recent chart version 27.0.2) disables the PVC mount. Is this intended? I noticed that my nexus pod's config does not survive e.g., deletions of the pod. When it starts back up, its like a clean install and the PVC always says (with kubectl describe) its not mounted.

several suggestions

Hi,

First of all, I am really looking forward providing helm chart officially. Now it is.

But I think this is early stage of chart.

1. when I use statefulset.enabled: true this chart does not work.
   and I want to know nexus support (need) statefulset or not really.

2. config does not support now.
   please refer to https://github.com/Oteemo/charts/blob/8f81bbda4913893fddeec7e6f9c033ce32e2a0a6/charts/sonatype-nexus/values.yaml#L207-L210
   Or how to use secret than configmap when I use for create file?

data:
  keycloak.json: |
    {
      "realm": "test",
      "auth-server-url": "https://company.net/keycloak/",
      "ssl-required": "external",
      "resource": "nexus",
      "credentials": {
        "secret": "blah"
      },
      "confidential-port": 0
    }

3. someone can not use docker repo. so I think ingress.yaml needs below

{{ if .Values.ingress.hostDocker }}
  - host: <snip>
{{ end }}

Thanks,

[nexus-repository-manager] Wrong default value in README.md

The default value of nexus.docker.enabled is discibed as True in the doc, but is False in the values.yaml.

A correction should be made in the doc, or in the values.yaml.

I can work on the PR, just tell me which one to modify.

Nexus Repository manager doesn't create emptyDir when persistence.enabled=false

I'm running the chart version 28.1.1 and set persistence=false but the pvc still been created and pods hang on pending state.

helm -n nexus install nexus sonatype/nexus-repository-manager --set-string persistence.enabled=false

helm pod describe:

  Type    Reason         Age                     From                         Message
  ----    ------         ----                    ----                         -------
  Normal  FailedBinding  <invalid> (x2 over 0s)  persistentvolume-controller  no persistent volumes available for this claim and no storage class is set

helm -n nexus get pvc:

NAME                                  STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   AGE
nexus-nexus-repository-manager-data   Pending                                                     5m27s

Default install for nexus-repository-manager not working

I try to do simple install on README.md but it is not working for default version, but when I use version 29.0.0 it is working. It affect when i use chart on Rancher Anyone know how to solve it?

Helm Repository not working

I followed the instructions provided at https://github.com/sonatype/helm3-charts/blob/main/docs/index.md

Adding the helm repository does not work:

$ helm repo add sonatype https://sonatype.github.io/helm3-charts/
Error: looks like "https://sonatype.github.io/helm3-charts/" is not a valid chart repository or cannot be reached: failed to fetch https://sonatype.github.io/helm3-charts/index.yaml : 404 Not Found

Here's my helm version:

$ helm version
version.BuildInfo{Version:"v3.6.3", GitCommit:"d506314abfb5d21419df8c7e7e68012379db2354", GitTreeState:"clean", GoVersion:"go1.16.5"}

[nexus-iq-server] Modify default password at install.

Is there a way we can autogenerate a password (or another solution) to populate the default admin account at runtime?

Ingress Issue

The ingress hosts are fixed within the ingress file template.
template/ingress.yaml
rules:
- host: iq-server.demo
http:
paths:
- path: {{ $ingressPath }}
backend:
serviceName: {{ $fullName }}
servicePort: 8070
- host: admin.iq-server.demo
http:
paths:
- path: {{ $ingressPath }}
backend:
serviceName: {{ $fullName }}
servicePort: 8071

Solution as follow:
template/ingress.yaml
rules:
- host: {{ (index .Values.ingress.hosts 0).host }}
http:
paths:
- path: {{ $ingressPath }}
backend:
serviceName: {{ $fullName }}
servicePort: 8070
- host: {{ (index .Values.ingress.hosts 1).host }}
http:
paths:
- path: {{ $ingressPath }}
backend:
serviceName: {{ $fullName }}
servicePort: 8071

Add namespace support

Hi!

It would be a nice feature to have the chart (NXRM at least, did not try IQ yet) supporting namespaces, through the --namespace option of Helm. It seems that it can only be deployed to the default namespace for now.

Maybe i'm not doing things right with this chart, i'm a total beginner with Helm :)

Does this chart provide ability to map to an external db

I am looking at the latest version of Nexus3 here.

Does this chart provide configuration options to map to an external database ?

Is IRSA supported for s3 blob stores ?

Hi team,

I was wondering if IRSA is a supported auth method for AWS S3 blob stores ? If not, do you have any plan of supporting it ?

Thank you!

[nexus-repository-manager] Add support for Prometheus metrics

Please add support for prometheus metrics

wrong NOTES.txt in chart

Here you got chart NOTES.txt inivoked after chart installation to forward port 8081 to 80 in the pod:

1. Get the application URL by running these commands:
  export POD_NAME=$(kubectl get pods --namespace default -l "app.kubernetes.io/name=nexus-repository-manager,app.kubernetes.io/instance=nexus" -o jsonpath="{.items[0].metadata.name}")
  kubectl --namespace default port-forward $POD_NAME 8081:80
  Your application is available at http://127.0.0.1

but pod which is created by chart is listening on port 8081 (as here

helm3-charts/charts/nexus-repository-manager/values.yaml

Line 45 in 777489d

nexusPort: 8081

)

This line

helm3-charts/charts/nexus-repository-manager/templates/NOTES.txt

Line 18 in 777489d

kubectl --namespace {{ .Release.Namespace }} port-forward $POD_NAME 8081:80

should be replaced by:

  kubectl --namespace {{ .Release.Namespace }} port-forward $POD_NAME 8081:{{ $.Values.nexus.nexusPort }}

and line

helm3-charts/charts/nexus-repository-manager/templates/NOTES.txt

Line 19 in 777489d

Your application is available at http://127.0.0.1

to:

  Your application is available at http://127.0.0.1:8081

nexus - volume error

Hi,

There's several volume issues.

item 1:
Recently volumeMounts: is newly added.

helm3-charts/nexus-repository-manager/templates/deployment.yaml

Lines 107 to 111 in 592c736

	volumeMounts:
	- mountPath: /nexus-data
	name: {{ template "nexus.fullname" . }}-data
	- mountPath: /nexus-data/backup
	name: {{ template "nexus.fullname" . }}-backup

But there's no volumes:
so here's error.

coalesce.go:199: warning: destination for data is a table. Ignoring non-table value []
Error: Deployment.apps "nexus-stage-nexus-repository-manager" is invalid: [spec.template.spec.containers[0].volumeMounts[0].name: Not found: "nexus-stage-nexus-repository-manager-data", spec.template.spec.containers[0].volumeMounts[1].name: Not found: "nexus-stage-nexus-repository-manager-backup"]

so you need to add (below is example)

        - name: {{ template "nexus.fullname" . }}-data
          {{- if .Values.persistence.enabled }}
          persistentVolumeClaim:
            claimName: {{ .Values.persistence.existingClaim | default (printf "%s-%s" (include "nexus.fullname" .) "data") }}
          {{- else }}
          emptyDir: {}
          {{- end }}

item 2: And I think you don't support backup feature now.
remove

            - mountPath: /nexus-data/backup	
              name: {{ template "nexus.fullname" . }}-backup

item 3: config's volumes and volumeMounts needed
add like

          volumeMounts:
            {{- if .Values.config.enabled }}
            - mountPath: {{ .Values.config.mountPath }}
              name: {{ template "nexus.name" . }}-conf
            {{- end }}

      volumes:
        {{- if .Values.config.enabled }}
        - name: {{ template "nexus.name" . }}-conf
          configMap:
            name: {{ template "nexus.name" . }}-conf
        {{- end }}

Nexus Behind Reverse Proxy Nginx

Hey Folks,
I've tried to follow this guide https://help.sonatype.com/repomanager3/installation/run-behind-a-reverse-proxy (and others) to access my nexus3 container.
However if I try to access it, I just see broken links as files can't be found.
I assume my nginx config is not working properly but I don't know which wheel needs to be turned here.
Is there anything special to be thought of with nexus in particular? Any basepath to be adjusted?

All hints highly appreciated.

My current nginx config:

apiVersion: v1
kind: ConfigMap
metadata:
  name: confnginx
data:
  nginx.conf: |

    upstream nexus-upstream {
      server nexus:8081;
    }
    server {
       listen 80;
       location /nexus/ {
       rewrite ^/nexus(.*) $1 break;
       proxy_pass http://nexus-upstream;
       proxy_set_header Host $host:$server_port;
       proxy_set_header X-Real-IP $remote_addr;
       proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        }
        }

My outcome within any browser:

Logs of the nginx which shows that required CSS files cant be found/accessed:

192.168.1.50 - - [02/Sep/2021:12:32:42 +0000] "GET /nexus/ HTTP/1.1" 200 8810 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-" 2021/09/02 12:32:42 [error] 23#23: *1 open() "/etc/nginx/html/static/rapture/resources/loading-prod.css" failed (2: No such file or directory), client: 192.168.1.50, server: , request: "GET /static/rapture/resources/loading-prod.css?_v=3.33.1-01&_e=OSS HTTP/1.1", host: "192.168.1.51", referrer: "http://192.168.1.51/nexus/" 192.168.1.50 - - [02/Sep/2021:12:32:42 +0000] "GET /static/rapture/resources/loading-prod.css?_v=3.33.1-01&_e=OSS HTTP/1.1" 404 555 "http://192.168.1.51/nexus/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-" 2021/09/02 12:32:42 [error] 23#23: *1 open() "/etc/nginx/html/static/rapture/resources/nexus-proui-plugin-prod.css" failed (2: No such file or directory), client: 192.168.1.50, server: , request: "GET /static/rapture/resources/nexus-proui-plugin-prod.css?_v=3.33.1-01&_e=OSS HTTP/1.1", host: "192.168.1.51", referrer: "http://192.168.1.51/nexus/" 192.168.1.50 - - [02/Sep/2021:12:32:42 +0000] "GET /static/rapture/resources/nexus-proui-plugin-prod.css?_v=3.33.1-01&_e=OSS HTTP/1.1" 404 555 "http://192.168.1.51/nexus/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-" 192.168.1.50 - - [02/Sep/2021:12:32:42 +0000] "GET /static/nexus-proui-bundle.css?_v=3.33.1-01&_e=OSS HTTP/1.1" 404 555 "http://192.168.1.51/nexus/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-" 2021/09/02 12:32:42 [error] 23#23: *3 open() "/etc/nginx/html/static/nexus-proui-bundle.css" failed (2: No such file or directory), client: 192.168.1.50, server: , request: "GET /static/nexus-proui-bundle.css?_v=3.33.1-01&_e=OSS HTTP/1.1", host: "192.168.1.51", referrer: "http://192.168.1.51/nexus/" 2021/09/02 12:32:42 [error] 23#23: *5 open() "/etc/nginx/html/static/rapture/resources/baseapp-prod.css" failed (2: No such file or directory), client: 192.168.1.50, server: , request: "GET /static/rapture/resources/baseapp-prod.css?_v=3.33.1-01&_e=OSS HTTP/1.1", host: "192.168.1.51", referrer: "http://192.168.1.51/nexus/" 192.168.1.50 - - [02/Sep/2021:12:32:42 +0000] "GET /static/rapture/resources/baseapp-prod.css?_v=3.33.1-01&_e=OSS HTTP/1.1" 404 555 "http://192.168.1.51/nexus/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-" 2021/09/02 12:32:42 [error] 23#23: *4 open() "/etc/nginx/html/static/rapture/resources/nexus-rapture-prod.css" failed (2: No such file or directory), client: 192.168.1.50, server: , request: "GET /static/rapture/resources/nexus-rapture-prod.css?_v=3.33.1-01&_e=OSS HTTP/1.1", host: "192.168.1.51", referrer: "http://192.168.1.51/nexus/" 192.168.1.50 - - [02/Sep/2021:12:32:42 +0000] "GET /static/rapture/resources/nexus-rapture-prod.css?_v=3.33.1-01&_e=OSS HTTP/1.1" 404 555 "http://192.168.1.51/nexus/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-" 2021/09/02 12:32:42 [error] 23#23: *7 open() "/etc/nginx/html/static/rapture/resources/nexus-coreui-plugin-prod.css" failed (2: No such file or directory), client: 192.168.1.50, server: , request: "GET /static/rapture/resources/nexus-coreui-plugin-prod.css?_v=3.33.1-01&_e=OSS HTTP/1.1", host: "192.168.1.51", referrer: "http://192.168.1.51/nexus/" 192.168.1.50 - - [02/Sep/2021:12:32:42 +0000] "GET /static/rapture/resources/nexus-coreui-plugin-prod.css?_v=3.33.1-01&_e=OSS HTTP/1.1" 404 555 "http://192.168.1.51/nexus/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-" 2021/09/02 12:32:42 [error] 23#23: *6 open() "/etc/nginx/html/static/rapture/resources/nexus-proximanova-plugin-prod.css" failed (2: No such file or directory), client: 192.168.1.50, server: , request: "GET /static/rapture/resources/nexus-proximanova-plugin-prod.css?_v=3.33.1-01&_e=OSS HTTP/1.1", host: "192.168.1.51", referrer: "http://192.168.1.51/nexus/" 192.168.1.50 - - [02/Sep/2021:12:32:42 +0000] "GET /static/rapture/resources/nexus-proximanova-plugin-prod.css?_v=3.33.1-01&_e=OSS HTTP/1.1" 404 555 "http://192.168.1.51/nexus/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-" 192.168.1.50 - - [02/Sep/2021:12:32:42 +0000] "GET /static/rapture/resources/nexus-onboarding-plugin-prod.css?_v=3.33.1-01&_e=OSS HTTP/1.1" 404 555 "http://192.168.1.51/nexus/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-" 2021/09/02 12:32:42 [error] 23#23: *1 open() "/etc/nginx/html/static/rapture/resources/nexus-onboarding-plugin-prod.css" failed (2: No such file or directory), client: 192.168.1.50, server: , request: "GET /static/rapture/resources/nexus-onboarding-plugin-prod.css?_v=3.33.1-01&_e=OSS HTTP/1.1", host: "192.168.1.51", referrer: "http://192.168.1.51/nexus/" 2021/09/02 12:32:42 [error] 23#23: *3 open() "/etc/nginx/html/static/nexus-rapture-bundle.css" failed (2: No such file or directory), client: 192.168.1.50, server: , request: "GET /static/nexus-rapture-bundle.css?_v=3.33.1-01&_e=OSS HTTP/1.1", host: "192.168.1.51", referrer: "http://192.168.1.51/nexus/" 192.168.1.50 - - [02/Sep/2021:12:32:42 +0000] "GET /static/nexus-rapture-bundle.css?_v=3.33.1-01&_e=OSS HTTP/1.1" 404 555 "http://192.168.1.51/nexus/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-" 192.168.1.50 - - [02/Sep/2021:12:32:42 +0000] "GET /static/nexus-coreui-bundle.css?_v=3.33.1-01&_e=OSS HTTP/1.1" 404 555 "http://192.168.1.51/nexus/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-" 2021/09/02 12:32:42 [error] 23#23: *5 open() "/etc/nginx/html/static/nexus-coreui-bundle.css" failed (2: No such file or directory), client: 192.168.1.50, server: , request: "GET /static/nexus-coreui-bundle.css?_v=3.33.1-01&_e=OSS HTTP/1.1", host: "192.168.1.51", referrer: "http://192.168.1.51/nexus/" 2021/09/02 12:32:42 [error] 23#23: *3 open() "/etc/nginx/html/static/rapture/baseapp-prod.js" failed (2: No such file or directory), client: 192.168.1.50, server: , request: "GET /static/rapture/baseapp-prod.js?_v=3.33.1-01&_e=OSS HTTP/1.1", host: "192.168.1.51", referrer: "http://192.168.1.51/nexus/" 192.168.1.50 - - [02/Sep/2021:12:32:42 +0000] "GET /static/rapture/baseapp-prod.js?_v=3.33.1-01&_e=OSS HTTP/1.1" 404 555 "http://192.168.1.51/nexus/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-" 2021/09/02 12:32:42 [error] 23#23: *5 open() "/etc/nginx/html/static/rapture/extdirect-prod.js" failed (2: No such file or directory), client: 192.168.1.50, server: , request: "GET /static/rapture/extdirect-prod.js?_v=3.33.1-01&_e=OSS HTTP/1.1", host: "192.168.1.51", referrer: "http://192.168.1.51/nexus/" 192.168.1.50 - - [02/Sep/2021:12:32:42 +0000] "GET /static/rapture/extdirect-prod.js?_v=3.33.1-01&_e=OSS HTTP/1.1" 404 555 "http://192.168.1.51/nexus/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-" 2021/09/02 12:32:42 [error] 23#23: *1 open() "/etc/nginx/html/static/nexus-coreui-bundle.js" failed (2: No such file or directory), client: 192.168.1.50, server: , request: "GET /static/nexus-coreui-bundle.js?_v=3.33.1-01&_e=OSS HTTP/1.1", host: "192.168.1.51", referrer: "http://192.168.1.51/nexus/" 192.168.1.50 - - [02/Sep/2021:12:32:42 +0000] "GET /static/nexus-coreui-bundle.js?_v=3.33.1-01&_e=OSS HTTP/1.1" 404 555 "http://192.168.1.51/nexus/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-" 2021/09/02 12:32:42 [error] 23#23: *6 open() "/etc/nginx/html/static/rapture/bootstrap.js" failed (2: No such file or directory), client: 192.168.1.50, server: , request: "GET /static/rapture/bootstrap.js?_v=3.33.1-01&_e=OSS HTTP/1.1", host: "192.168.1.51", referrer: "http://192.168.1.51/nexus/"

bad notes formatting when ingress is enabled

When ingress is enabled, NOTES.txt use .Values.ingress.hosts to build urls but that value appears to be empty.

So your release notes ends with:
`...

1. Get the application URL by running these commands:
   `

you can't set the nodeport number on service

Unable to set custom ingress host

Are these 2 lines correct?

https://github.com/sonatype/helm3-charts/blob/master/nexus-iq/templates/ingress.yaml#L31
https://github.com/sonatype/helm3-charts/blob/master/nexus-iq/templates/ingress.yaml#L38

[nexus-repository-manager] Make TLS optional for the Docker registry ingress

TLS is optional for the ingress.hostRepo but not for Docker registries, which make a certificate mandatory. To simplify the use of docker registries, TLS should be made optionnal.

I could work on the PR if needed.

Ingress annotations are shared between web ingress and docker registry ingress

Hello,

Context:

• We use helm chart to deploy Nexus on EKS using an ALB (application Load Balancer).
• ALB use specifics ingress annotation for health check
  (full list here)

alb.ingress.kubernetes.io/healthcheck-port
alb.ingress.kubernetes.io/healthcheck-protocol
alb.ingress.kubernetes.io/healthcheck-path
alb.ingress.kubernetes.io/success-codes

Problem:
The health check URL for nexus web service is "/" with a return code 200
The health check URL for the docker registry service is "/v2/" with a return code 200 or 401

Actually the chart give the possibility to customise annotation only for all ingress

Idea of solution:

Add a nexus.docker.registries.ingress.annotations or a ingress.registries.annotations and add them to https://github.com/sonatype/helm3-charts/blob/main/charts/nexus-repository-manager/templates/ingress.yaml#L54 as extra annotation

[nexus-repository-manager] Bug in NOTES.txt

{{ . }} texts exists in templates/NOTES.txt file.
1. Get the application URL by running these commands: {{- if .Values.ingress.enabled }} http{{ if $.Values.ingress.tls }}s{{ end }}://{{ $.Values.ingress.hostRepo }}{{ . }}

It causes printing toString() output of spec yaml on deployments...
[...id.commap[Capabilities:0xc0004cbb90 Chart:0xc00095c480 Files:map[.helmignore:[35 32 80 97 116 116 101 114 110 115 32 116 111 32 105 103 110 111 114 101 32 119 104 101 110 32 98 117 105 108 100 105 110 103 32 112 97 99 107 97 103 101 115 46 10 35...]

Provide option to use non-beta API, some beta APIs are now deprecated

Eventually, kubernetes 1.22 will come and those beta APIs will be removed
$ helm install nexus -f nexus-values.yaml sonatype/nexus-repository-manager --namespace nexus-project
W0501 22:30:31.490411 5728 warnings.go:67] networking.k8s.io/v1beta1 Ingress is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress

bug: env var install4jAddVmParams does not exist in the nexus image

pr for fixing the bug: #81

Docker Ingress Labels & Annotations Configuration

In the current ingress.yaml context there is no way to define specific ingress labels & annotations cause they are all inherit from the nexus manager ingress resource.

remove prestart

Hi,

Actually Kubernetes does not support preStart syntax.

helm3-charts/nexus-repository-manager/templates/deployment.yaml

Line 70 in f1f549d

preStart:

Configmap name mismatch

iqserver.fullname is used for the configmap in the deployment:

helm3-charts/nexus-iq/templates/deployment.yaml

Lines 67 to 69 in ea924ce

	- name: config-volume
	configMap:
	name: {{ template "iqserver.fullname" . }}

But it is generated as iqserver.fullname-conf

helm3-charts/nexus-iq/templates/configmap.yaml

Line 4 in ea924ce

name: {{ template "iqserver.fullname" . }}-conf

Causing: MountVolume.SetUp failed for volume "config-volume" : configmap "nexus-iq-nexus-iq-server" not found

In my case the configmap was installed to nexus-iq-nexus-iq-server-conf which did not equal nexus-iq-nexus-iq-server and caused the error above.

How to use a local persistent volume claim?

The sample values.yml only contains a pdName variable, I think this is for Google Cloud, right?

How would I use a local volume claim?

in NOTES.txt at $.Valuies.ingress.hostRepo.host can't evaluate field host

With 23.1.5 this evening, I get this:

Error: Failed to render chart: exit status 1: Error: template: nexus-repository-manager/templates/NOTES.txt:3:52: executing "nexus-repository-manager/templates/NOTES.txt" at <$.Values.ingress.hostRepo.host>: can't evaluate field host in type interface {}
Use --debug flag to render out invalid YAML
Error: plugin "diff" exited with error

Image pull secrets not working as aspected

helm3-charts/charts/nexus-repository-manager/templates/deployment.yaml

Line 51 in 777489d

{{- if .Values.nexus.imagePullSecrets }}

      imagePullSecrets:
        {{- toYaml . | nindent 8 }}
      {{- end }}

should be something like :

      imagePullSecrets:
        {{- toYaml  .Values.nexus.imagePullSecrets  | nindent 8 }}
      {{- end }}

or :

      imagePullSecrets:
        {{- with ..Values.nexus.imagePullSecrets }}
          {{ toYaml . | nindent 8 }}
        {{- end }}
      {{- end }}

The imagePullSecret value inside

helm3-charts/charts/nexus-repository-manager/values.yaml

Line 70 in 777489d

imagePullSecrets: []

in on the main layer and not in the nexus chapter (but should be on nexus layer).

Incorrect indentation

The annotations field indentation appears to be incorrect here:

helm3-charts/nexus-iq/templates/persistentVolumeClaim.yaml

Line 13 in 1c0a876

annotations:

While installing the nexus iq chart with annotations enabled for pvc, it throws an error:
error validating "": error validating data: ValidationError(PersistentVolumeClaim): unknown field "annotations" in io.k8s.api.core.v1.PersistentVolumeClaim

A quick glimpse at the api - kubectl explain PersistentVolumeClaim.metadata | less suggests that the annotations field should come under metadata resource at the same level as name and labels. The following seems to fix the issue for me.

metadata:
  name: {{ template "iqserver.fullname" . }}-data
  ...
  annotations:
  {{ toYaml .Values.persistence.annotations | indent 2 }}
  ...

nexus authentication configuration

It would be beneficial if the nexus-repository-manager supported configuring saml and/or ldap configuration through the helm chart deployment along with licenses. Also, what is the supported values for the configmap? Is it json, yaml, properties?

container repository ingress configuration

It would be nice if the container registry ingress configuration was better documented, we got it working after significant strife in reverse engineering how the template/ingress.yaml was being read.

Also, for cert-manager to generate certificates for both of our nexus and container registry domains, we ended up having to create a separate ingress rule as cert-manager didn't add both ingress.tls.hosts to the secret.

Separately, what about multiple container repositories? Can they be collapsed onto the same port or do we need a separate fqdn/certificate/port for each one?

[nexus-repository-manager] Have a way to override hardcoded number of replicas (Deployment)

Currently the number of replicas is hardcoded to 1.

Is there any reason why we can't override it?

Can not upgrade with rancher, as latest version seems to be 29.1.0, which is not available

When upgrading with rancher, using catalog https://sonatype.github.io/helm3-charts/, there is a 404 http response on this url https://github.com/sonatype/helm3-charts/releases/download/nexus-repository-manager-29.1.0/nexus-repository-manager-29.1.0.tgz.
This blocks any upgrade with rancher, as rancher seems to need the latest version available before going any further.

Typo in values.yaml

-I suppose that "serviceType" should be changed to "type".

https://github.com/sonatype/helm3-charts/blob/master/charts/nexus-repository-manager/values.yaml

...
service:
  ...
  serviceType: ClusterIP

https://github.com/sonatype/helm3-charts/blob/master/charts/nexus-repository-manager/templates/service.yaml#L19

...
spec:
  type: {{ .Values.service.type }}

Error with HTTPS : Mixed Content: The page at was loaded over HTTPS, but requested an insecure stylesheet

Mixed Content: The page at was loaded over HTTPS, but requested an insecure stylesheet
This request has been blocked; the content must be served over HTTPS.

[nexus-repository-manager] properties override results on permissions issues on nexus-data

On the values file I enabled the properties override a s follow:

properties:
  override: true
  data: 
    nexus.scripts.allowCreation: true

Then install failed with following error:

2021-03-19 11:11:31,229+0000 INFO  [jetty-main-1] *SYSTEM org.eclipse.jetty.server.session - node0 Stopped scavenging
2021-03-19 11:11:31,231+0000 ERROR [jetty-main-1] *SYSTEM org.sonatype.nexus.bootstrap.jetty.JettyServer - Failed to start
com.google.inject.ProvisionException: Unable to provision, see the following errors:

1) Error injecting constructor, java.lang.RuntimeException: java.nio.file.AccessDeniedException: /nexus-data/etc/logback
  at org.sonatype.nexus.internal.log.LogbackLoggerOverrides.<init>(LogbackLoggerOverrides.java:67)
  at / (via modules: org.sonatype.nexus.extender.modules.NexusBundleModule -> org.eclipse.sisu.space.SpaceModule)
  while locating org.sonatype.nexus.internal.log.LogbackLoggerOverrides
  while locating java.lang.Object annotated with *
  at org.eclipse.sisu.wire.LocatorWiring
  while locating org.sonatype.nexus.internal.log.LoggerOverrides
    for the 3rd parameter of org.sonatype.nexus.internal.log.LogbackLogManager.<init>(LogbackLogManager.java:86)
  at / (via modules: org.sonatype.nexus.extender.modules.NexusBundleModule -> org.eclipse.sisu.space.SpaceModule)
  while locating org.sonatype.nexus.internal.log.LogbackLogManager
  while locating java.lang.Object annotated with *

1 error
        at com.google.inject.internal.InternalProvisionException.toProvisionException(InternalProvisionException.java:226)
        at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1097)
        at org.eclipse.sisu.inject.LazyBeanEntry.getValue(LazyBeanEntry.java:81)
        at org.sonatype.nexus.extender.NexusLifecycleManager.to(NexusLifecycleManager.java:111)
        at org.sonatype.nexus.extender.NexusContextListener.moveToPhase(NexusContextListener.java:321)
        at org.sonatype.nexus.extender.NexusContextListener.contextInitialized(NexusContextListener.java:181)
        at org.sonatype.nexus.bootstrap.osgi.ListenerTracker.addingService(ListenerTracker.java:47)
        at org.sonatype.nexus.bootstrap.osgi.ListenerTracker.addingService(ListenerTracker.java:1)
        at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)
        at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870)
        at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
        at org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:183)
        at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:318)
        at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:261)
        at org.sonatype.nexus.bootstrap.osgi.BootstrapListener.contextInitialized(BootstrapListener.java:129)
        at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:1068)
        at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:572)
        at org.eclipse.jetty.server.handler.ContextHandler.contextInitialized(ContextHandler.java:997)
        at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:754)
        at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:379)
        at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1457)
        at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1422)
        at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:911)
        at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:288)
        at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:524)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:72)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
        at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
        at com.codahale.metrics.jetty9.InstrumentedHandler.doStart(InstrumentedHandler.java:101)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:72)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
        at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:72)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
        at org.eclipse.jetty.server.Server.start(Server.java:423)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
        at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
        at org.eclipse.jetty.server.Server.doStart(Server.java:387)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:72)
        at org.sonatype.nexus.bootstrap.jetty.JettyServer$JettyMainThread.run(JettyServer.java:274)
Caused by: java.lang.RuntimeException: java.nio.file.AccessDeniedException: /nexus-data/etc/logback
        at org.sonatype.nexus.internal.app.ApplicationDirectoriesImpl.mkdir(ApplicationDirectoriesImpl.java:116)
        at org.sonatype.nexus.internal.app.ApplicationDirectoriesImpl.resolve(ApplicationDirectoriesImpl.java:134)
        at org.sonatype.nexus.internal.app.ApplicationDirectoriesImpl.getWorkDirectory(ApplicationDirectoriesImpl.java:95)
        at org.sonatype.nexus.internal.app.ApplicationDirectoriesImpl.getWorkDirectory(ApplicationDirectoriesImpl.java:100)
        at org.sonatype.nexus.internal.log.LogbackLoggerOverrides.<init>(LogbackLoggerOverrides.java:69)
        at org.sonatype.nexus.internal.log.LogbackLoggerOverrides$$FastClassByGuice$$d577229d.newInstance(<generated>)
        at com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:89)
        at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:114)
        at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:91)
        at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:306)
        at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
        at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:168)
        at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:39)
        at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:62)
        at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1094)
        at org.eclipse.sisu.inject.LazyBeanEntry.getValue(LazyBeanEntry.java:81)
        at org.eclipse.sisu.wire.BeanProviders.firstOf(BeanProviders.java:179)
        at org.eclipse.sisu.wire.BeanProviders$7.get(BeanProviders.java:160)
        at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:85)
        at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:57)
        at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:59)
        at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47)
        at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:42)
        at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:65)
        at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:113)
        at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:91)
        at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:306)
        at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
        at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:168)
        at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:39)
        at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:62)
        at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1094)
        ... 40 common frames omitted
Caused by: java.nio.file.AccessDeniedException: /nexus-data/etc/logback
        at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)
        at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
        at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
        at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384)
        at java.nio.file.Files.createDirectory(Files.java:674)
        at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781)
        at java.nio.file.Files.createDirectories(Files.java:767)
        at org.sonatype.nexus.common.io.DirectoryHelper.mkdir(DirectoryHelper.java:143)
        at org.sonatype.nexus.internal.app.ApplicationDirectoriesImpl.mkdir(ApplicationDirectoriesImpl.java:110)
        ... 71 common frames omitted

I also tried with the following init container to fix the permissions, but that does not help

  deployment:
    initContainers:
    - name: fmp-volume-permission
      image: busybox
      imagePullPolicy: IfNotPresent
      command: ['chmod','-R', '777', '/nexus-data']
      volumeMounts:
        - name: nexus-repository-manager-data
          mountPath: /nexus-data

Kubernetes version:

Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.0", GitCommit:"af46c47ce925f4c4ad5cc8d1fca46c7b77d13b38", GitTreeState:"clean", BuildDate:"2020-12-08T17:59:43Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16+", GitVersion:"v1.16.15-gke.7800", GitCommit:"cef3156c566a1d1a4b23ee360a760f45bfbaaac1", GitTreeState:"clean", BuildDate:"2020-12-14T09:12:37Z", GoVersion:"go1.13.15b4", Compiler:"gc", Platform:"linux/amd64"}