mirror of
https://github.com/bitnami/charts.git
synced 2026-03-14 14:57:22 +08:00
[bitnami/*] Move documentation sections from docs.bitnami.com back to the README (#22203)
* [bitnami/*] Move documentation sections from docs.bitnami.com back to the README Signed-off-by: Jota Martos <jotamartos@vmware.com> * [bitnami/*] Move use-external-database section to GitHub Signed-off-by: Jota Martos <jotamartos@vmware.com> * [bitnami/*] Move configure-sidecar-init-containers section to GitHub Signed-off-by: Jota Martos <jotamartos@vmware.com> * [bitnami/*] Move configure-sidecar-init-containers section to GitHub Signed-off-by: Jota Martos <jotamartos@vmware.com> * [bitnami/*] Move configure-ingress section to GitHub Signed-off-by: Jota Martos <jotamartos@vmware.com> * [bitnami/*] Move enable-tls-ingress section to GitHub Signed-off-by: Jota Martos <jotamartos@vmware.com> * [bitnami/*] Remove upgrade-helm3 section to GitHub Signed-off-by: Jota Martos <jotamartos@vmware.com> * [bitnami/*] Move upgrade section to GitHub Signed-off-by: Jota Martos <jotamartos@vmware.com> * [bitnami/*] Move upgrade section to GitHub Signed-off-by: Jota Martos <jotamartos@vmware.com> * [bitnami/*] Move configure-sidecar-init-containers section to GitHub Signed-off-by: Jota Martos <jotamartos@vmware.com> * [bitnami/*] Remove get-started link in GitHub Signed-off-by: Jota Martos <jotamartos@vmware.com> * [bitnami/*] Move rest of docs sections to GitHub Signed-off-by: Jota Martos <jotamartos@vmware.com> * [CONTENT-6404] Remove some docs.bitnami.com urls from the READMEs Signed-off-by: Jota Martos <jotamartos@vmware.com> * [bitnami/*] Fix linter Signed-off-by: Jota Martos <jotamartos@vmware.com> * [bitnami/*] Fix linter Signed-off-by: Jota Martos <jotamartos@vmware.com> * [bitnami/*] Fix linter Signed-off-by: Jota Martos <jotamartos@vmware.com> * [bitnami/*] Fix linter Signed-off-by: Jota Martos <jotamartos@vmware.com> * [bitnami/*] Ignore img folder when packaging the helm chart Signed-off-by: Jota Martos <jotamartos@vmware.com> * [bitnami/*] Update template's README file Signed-off-by: Jota Martos <jotamartos@vmware.com> --------- Signed-off-by: Jota Martos <jotamartos@vmware.com> Signed-off-by: Juan José Martos <jotamartos@gmail.com>
This commit is contained in:
Juan José Martos
23
bitnami/haproxy/.helmignore
Normal file
23
bitnami/haproxy/.helmignore
Normal file
@@ -0,0 +1,23 @@
|
||||
# Patterns to ignore when building packages.
|
||||
# This supports shell glob matching, relative path matching, and
|
||||
# negation (prefixed with !). Only one pattern per line.
|
||||
.DS_Store
|
||||
# Common VCS dirs
|
||||
.git/
|
||||
.gitignore
|
||||
.bzr/
|
||||
.bzrignore
|
||||
.hg/
|
||||
.hgignore
|
||||
.svn/
|
||||
# Common backup files
|
||||
*.swp
|
||||
*.bak
|
||||
*.tmp
|
||||
*~
|
||||
# Various IDEs
|
||||
.project
|
||||
.idea/
|
||||
*.tmproj
|
||||
# img folder
|
||||
img/
|
||||
@@ -24,8 +24,6 @@ This chart bootstraps a [HAProxy](https://github.com/haproxytech/haproxy) Deploy
|
||||
|
||||
Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
|
||||
|
||||
[Learn more about the default configuration of the chart](https://docs.bitnami.com/kubernetes/infrastructure/haproxy/get-started/).
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- Kubernetes 1.23+
|
||||
@@ -242,9 +240,58 @@ Bitnami will release a new chart updating its containers if a new version of the
|
||||
By default, HAProxy is deployed with a sample, non-functional, configuration. You will need to edit the following values to adapt it to your use case:
|
||||
|
||||
- Set the configuration to be injected in the `haproxy.cfg` file by changing the `configuration` parameter. Alternatively, you can provide an existing ConfigMap with `haproxy.cfg` by using the `existingConfigmap` parameter.
|
||||
|
||||
The example below configures HAProxy to forward all requests to port 8080 to a service called *service1:8080* (it is assumed that this is accessible from inside the cluster).
|
||||
|
||||
```yaml
|
||||
configuration: |
|
||||
global
|
||||
log 127.0.0.1 local2
|
||||
maxconn 4096
|
||||
|
||||
defaults
|
||||
mode http
|
||||
log global
|
||||
option httplog
|
||||
option dontlognull
|
||||
option http-server-close
|
||||
option forwardfor except 127.0.0.0/8
|
||||
option redispatch
|
||||
retries 3
|
||||
timeout http-request 20s
|
||||
timeout queue 1m
|
||||
timeout connect 10s
|
||||
timeout client 1m
|
||||
timeout server 1m
|
||||
timeout http-keep-alive 30s
|
||||
timeout check 10s
|
||||
maxconn 3000
|
||||
|
||||
frontend fe_http
|
||||
option forwardfor except 127.0.0.1
|
||||
option httpclose
|
||||
bind *:8080
|
||||
default_backend be_http
|
||||
|
||||
backend be_http
|
||||
balance roundrobin
|
||||
server nginx service:8080 check port 8080
|
||||
```
|
||||
|
||||
- Based on your HAProxy configuration, edit the `containerPorts` and `service.ports` parameters. In the `containerPorts` parameter, set all the ports that the HAProxy configuration uses, and in the `service.ports` parameter, set the ports to be externally exposed.
|
||||
|
||||
Refer to the [chart documentation for a more detailed configuration example](https://docs.bitnami.com/kubernetes/infrastructure/haproxy/get-started/configure-proxy).
|
||||
For the example above, the configuration would look like this:
|
||||
|
||||
```yaml
|
||||
service:
|
||||
- name: http
|
||||
port: 80 # We use port 80 in the service
|
||||
targetPort: http
|
||||
|
||||
containerPorts:
|
||||
- name: http
|
||||
containerPort: 8080
|
||||
```
|
||||
|
||||
### Add extra environment variables
|
||||
|
||||
@@ -260,9 +307,43 @@ Alternatively, use a ConfigMap or a Secret with the environment variables. To do
|
||||
|
||||
### Use Sidecars and Init Containers
|
||||
|
||||
If additional containers are needed in the same pod (such as additional metrics or logging exporters), they can be defined using the `sidecars` config parameter. Similarly, extra init containers can be added using the `initContainers` parameter.
|
||||
If additional containers are needed in the same pod (such as additional metrics or logging exporters), they can be defined using the `sidecars` config parameter.
|
||||
|
||||
Refer to the chart documentation for more information on, and examples of, configuring and using [sidecars and init containers](https://docs.bitnami.com/kubernetes/infrastructure/haproxy/configuration/configure-sidecar-init-containers/).
|
||||
```yaml
|
||||
sidecars:
|
||||
- name: your-image-name
|
||||
image: your-image
|
||||
imagePullPolicy: Always
|
||||
ports:
|
||||
- name: portname
|
||||
containerPort: 1234
|
||||
```
|
||||
|
||||
If these sidecars export extra ports, extra port definitions can be added using the `service.extraPorts` parameter (where available), as shown in the example below:
|
||||
|
||||
```yaml
|
||||
service:
|
||||
extraPorts:
|
||||
- name: extraPort
|
||||
port: 11311
|
||||
targetPort: 11311
|
||||
```
|
||||
|
||||
> NOTE: This Helm chart already includes sidecar containers for the Prometheus exporters (where applicable). These can be activated by adding the `--enable-metrics=true` parameter at deployment time. The `sidecars` parameter should therefore only be used for any extra sidecar containers.
|
||||
|
||||
If additional init containers are needed in the same pod, they can be defined using the `initContainers` parameter. Here is an example:
|
||||
|
||||
```yaml
|
||||
initContainers:
|
||||
- name: your-image-name
|
||||
image: your-image
|
||||
imagePullPolicy: Always
|
||||
ports:
|
||||
- name: portname
|
||||
containerPort: 1234
|
||||
```
|
||||
|
||||
Learn more about [sidecar containers](https://kubernetes.io/docs/concepts/workloads/pods/) and [init containers](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/).
|
||||
|
||||
### Set Pod affinity
|
||||
|
||||
@@ -288,4 +369,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.
|
||||
|
||||
Reference in New Issue
Block a user