mirror of
https://github.com/bitnami/charts.git
synced 2026-03-27 15:27:10 +08:00
[bitnami/charts] Apply linter to README files (#15357)
* Fix markdown linter issues in all markdown files present in this repo Signed-off-by: Fran Mulero <fmulero@vmware.com> * Apply markdown fixes Signed-off-by: Fran Mulero <fmulero@vmware.com> * Update README.md with readme-generator-for-helm Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> * Remove appsmith empty section Signed-off-by: Fran Mulero <fmulero@vmware.com> --------- Signed-off-by: Fran Mulero <fmulero@vmware.com> Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> Co-authored-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
@@ -6,8 +6,6 @@ Harbor is an open source trusted cloud-native registry to store, sign, and scan
|
||||
|
||||
[Overview of Harbor](https://goharbor.io/)
|
||||
|
||||
|
||||
|
||||
## TL;DR
|
||||
|
||||
```console
|
||||
@@ -598,7 +596,7 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
|
||||
|
||||
| Name | Description | Value |
|
||||
| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
|
||||
| `registry.secret` | Secret is used to secure the upload state from client and registry storage backend. See: https://github.com/docker/distribution/blob/master/docs/configuration.md | `""` |
|
||||
| `registry.secret` | Secret is used to secure the upload state from client and registry storage backend. See: <https://github.com/docker/distribution/blob/master/docs/configuration.md> | `""` |
|
||||
| `registry.existingSecret` | Existing secret for registry | `""` |
|
||||
| `registry.relativeurls` | Make the registry return relative URLs in Location headers. The client is responsible for resolving the correct URL. | `false` |
|
||||
| `registry.credentials.username` | The username for accessing the registry instance, which is hosted by htpasswd auth mode. More details see [official docs](https://github.com/docker/distribution/blob/master/docs/configuration.md#htpasswd) | `harbor_registry_user` |
|
||||
@@ -1172,6 +1170,7 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
|
||||
| `metrics.serviceMonitor.honorLabels` | Specify honorLabels parameter to add the scrape endpoint | `false` |
|
||||
| `metrics.serviceMonitor.jobLabel` | The name of the label on the target service to use as the job name in prometheus. | `""` |
|
||||
|
||||
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
|
||||
|
||||
```console
|
||||
helm install my-release \
|
||||
@@ -1327,4 +1326,4 @@ Unless required by applicable law or agreed to in writing, software
|
||||
distributed under the License is distributed on an "AS IS" BASIS,
|
||||
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
||||
See the License for the specific language governing permissions and
|
||||
limitations under the License.
|
||||
limitations under the License.
|
||||
|
||||
@@ -1905,7 +1905,7 @@ jobservice:
|
||||
## Registry Parameters
|
||||
##
|
||||
registry:
|
||||
## @param registry.secret Secret is used to secure the upload state from client and registry storage backend. See: https://github.com/docker/distribution/blob/master/docs/configuration.md
|
||||
## @param registry.secret Secret is used to secure the upload state from client and registry storage backend. See: <https://github.com/docker/distribution/blob/master/docs/configuration.md>
|
||||
## and registry storage backend.
|
||||
## See: https://github.com/docker/distribution/blob/master/docs/configuration.md#http
|
||||
## If a secret key is not specified, Helm will generate one.
|
||||
|
||||
Reference in New Issue
Block a user