Bitnami/charts
2
0
Fork 0
mirror of https://github.com/bitnami/charts.git synced 2026-04-02 15:27:08 +08:00
Code Issues Packages Projects Releases Wiki Activity

Standardize component.name & component.fullname functions

Browse Source 
Signed-off-by: juan131 <juan@bitnami.com>
This commit is contained in:
juan131
2019-07-10 11:59:36 +02:00
parent 54123018c8
commit 775948eb27
139 changed files with 732 additions and 269 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
bitnami/harbor/README.md
View File

@@ -147,6 +147,8 @@ The following table lists the configurable parameters of the Harbor chart and th
| `persistence.imageChartStorage.disableredirect` | The configuration for managing redirects from content backends. For backends which do not supported it (such as using minio for `s3` storage type), please set it to `true` to disable redirects. Refer to the [guide](https://github.com/docker/distribution/blob/master/docs/configuration.md#redirect) for more information about the detail | `false` |
| `persistence.imageChartStorage.type` | The type of storage for images and charts: `filesystem`, `azure`, `gcs`, `s3`, `swift` or `oss`. The type must be `filesystem` if you want to use persistent volumes for registry and chartmuseum. Refer to the [guide](https://github.com/docker/distribution/blob/master/docs/configuration.md#storage) for more information about the detail | `filesystem` |
| **General** |
| `nameOverride` | String to partially override harbor.fullname template with a string (will prepend the release name) | `nil` |
| `fullnameOverride` | String to fully override harbor.fullname template with a string | `nil` |
| `externalURL` | The external URL for Harbor core service | `https://core.harbor.domain` |
| `imagePullPolicy` | The image pull policy | `IfNotPresent` |
| `logLevel` | The log level | `debug` |
@@ -344,4 +346,4 @@ This chart includes a `values-production.yaml` file where you can find some para
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.