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

[bitnami/*] Remove relative links to non-README sections, add verification for that and update TL;DR section (#20967)

Browse Source 
* [bitnami/*] Remove relative links to non-README sections and add verification

Signed-off-by: Jota Martos <jotamartos@vmware.com>

* Update Elasticsearch solution title

Signed-off-by: Jota Martos <jotamartos@vmware.com>

* Update .github/workflows/markdown-linter.yml

Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>

* Move enterprise string to the tl;dr section

Signed-off-by: Jota Martos <jotamartos@vmware.com>

* Fix typo in some READMEs

Signed-off-by: Jota Martos <jotamartos@vmware.com>

* Replace placeholders in the TLDR section

Signed-off-by: Jota Martos <jotamartos@vmware.com>

* Fix typo in some READMEs

Signed-off-by: Jota Martos <jotamartos@vmware.com>

* Revert "Update Elasticsearch solution title"

This reverts commit 9f437f993d14f69a1ffffbcec78a5df8654aaefd.

---------

Signed-off-by: Jota Martos <jotamartos@vmware.com>
Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>
Co-authored-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>
This commit is contained in:
Juan José Martos
2023-11-16 15:18:56 +01:00
committed by GitHub
parent 05ab715c7d
commit 11036334d8
108 changed files with 370 additions and 577 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
bitnami/nginx-ingress-controller/README.md
View File

@@ -11,10 +11,10 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
## TL;DR
```console
helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/nginx-ingress-controller
helm install my-release oci://registry-1.docker.io/bitnamicharts/nginx-ingress-controller
```
> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
Looking to use NGINX Ingress Controller in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
## Introduction
@@ -24,8 +24,6 @@ This chart bootstraps a [ingress-nginx](https://github.com/kubernetes/ingress-ng
Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
Looking to use NGINX Ingress Controller in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
## Prerequisites
- Kubernetes 1.23+
@@ -350,7 +348,7 @@ helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/nginx
```
> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
> **Tip**: You can use the default [values.yaml](values.yaml)
> **Tip**: You can use the default [values.yaml](https://github.com/bitnami/charts/tree/main/bitnami/nginx-ingress-controller/values.yaml)
## Configuration and installation details