This is a helm-chart for [nexxus]
This chart is part of the DevOpsKube package.
It is right now fully based on the bitnami redmine chart.
this url is password protected, therefor this can not get called without username password
livenessProbe: httpGet: path: /service/metrics/ping port: http initialDelaySeconds: 120 timeoutSeconds: 5 readinessProbe: httpGet: path: /service/metrics/ping port: http initialDelaySeconds: 5 timeoutSeconds: 1
This chart uses the following sub-dependencies:
To be able to use this package, the following variables should be set.
provide git as a scm system, does not seem to work right now.
Nexus is the world's only repository manager with FREE support for popular formats..
Right now we do use version 3.0.2.
This chart uses the docker image from sonatype.
Get this Chart
Our central repository is located at:
https://devopsku.be/charts, please configure this in your helm installation (via
helm repo add). Then you can download and install this chart using the usual helm procedure (see Using Helm).
If you would like to contribute and/or like to make changes on this chart, please clone this repo via:
git clone https://github.com/devopskube/devopskube.git
Installing the chart
Other installation-instructions can be found on the above mentioned Using Helm page.
The following tables lists the configurable parameters of the Nexus chart and their default values.
||Host Name of this Instance||
||Port of the container||
||Resource limit memory (-Xmx)||
||Minimum Memory (-Xms)||
||Additional options for the JVM||''|
||Path where all data on the host is stored||
Specify each parameter using the --set key=value[,key=value] argument to helm install.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
$ helm install --name my-nexus -f values.private.yaml nexus-x.x.x.tgz
Tip: You can use the default values.yaml
The initial Username/Pasword combination for the first login is:
To be able to keep stateful data in the nexus kubernetes container, the following path is used:
Right now, we do use HostPathes, which do not work in a real cluster environment (like AWS or GCE). Please adopt this one to your own needs.
The above mentioned path should be read/writable on the host for the user 1000.
- Provide more initial configurations (smtp-settings, ldap-settings, ...)
- use LDAP and SSO