Difference between revisions of "Helm install ingress-nginx"
Jump to navigation
Jump to search
Line 9: | Line 9: | ||
== Example == | == Example == | ||
+ | |||
+ | NAME: my-ingress-nginx | ||
+ | LAST DEPLOYED: Wed Nov 8 20:56:33 2023 | ||
+ | NAMESPACE: default | ||
+ | STATUS: deployed | ||
+ | REVISION: 1 | ||
+ | TEST SUITE: None | ||
+ | NOTES: | ||
+ | The ingress-nginx controller has been installed. | ||
+ | It may take a few minutes for the LoadBalancer IP to be available. | ||
+ | You can watch the status by running 'kubectl --namespace default get services -o wide -w my-ingress-nginx-controller' | ||
+ | |||
+ | An example Ingress that makes use of the controller: | ||
+ | apiVersion: networking.k8s.io/v1 | ||
+ | kind: Ingress | ||
+ | metadata: | ||
+ | name: example | ||
+ | namespace: foo | ||
+ | spec: | ||
+ | ingressClassName: nginx | ||
+ | rules: | ||
+ | - host: www.example.com | ||
+ | http: | ||
+ | paths: | ||
+ | - pathType: Prefix | ||
+ | backend: | ||
+ | service: | ||
+ | name: exampleService | ||
+ | port: | ||
+ | number: 80 | ||
+ | path: / | ||
+ | # This section is only required if TLS is to be enabled for the Ingress | ||
+ | tls: | ||
+ | - hosts: | ||
+ | - www.example.com | ||
+ | secretName: example-tls | ||
<pre> | <pre> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
If TLS is enabled for the Ingress, a Secret containing the certificate and key must also be provided: | If TLS is enabled for the Ingress, a Secret containing the certificate and key must also be provided: | ||
Revision as of 20:04, 8 November 2023
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo update helm install my-ingress-nginx ingress-nginx/ingress-nginx
helm install my-release oci://ghcr.io/nginxinc/charts/nginx-ingress --version 0.18.0
Example
NAME: my-ingress-nginx LAST DEPLOYED: Wed Nov 8 20:56:33 2023 NAMESPACE: default STATUS: deployed REVISION: 1 TEST SUITE: None NOTES: The ingress-nginx controller has been installed. It may take a few minutes for the LoadBalancer IP to be available. You can watch the status by running 'kubectl --namespace default get services -o wide -w my-ingress-nginx-controller' An example Ingress that makes use of the controller: apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: example namespace: foo spec: ingressClassName: nginx rules: - host: www.example.com http: paths: - pathType: Prefix backend: service: name: exampleService port: number: 80 path: / # This section is only required if TLS is to be enabled for the Ingress tls: - hosts: - www.example.com secretName: example-tls
If TLS is enabled for the Ingress, a Secret containing the certificate and key must also be provided: apiVersion: v1 kind: Secret metadata: name: example-tls namespace: foo data: tls.crt: <base64 encoded cert> tls.key: <base64 encoded key> type: kubernetes.io/tls
Related
- NGINX Ingress Controller
- kubectl --namespace default get services -o wide -w my-ingress-nginx-controller
See also
- NGINX Ingress Controller: ConfigMap ingress-nginx,
UnAvailableLoadBalancer, UpdatedLoadBalancer, ingress-nginx-controller, ingress-nginx-controller-controller-admission, nginx.org/ingress-controller
- Web server: Nginx:
/etc/nginx/nginx.conf
,nginx -t
, Nginx logs, Nginx change log, PHP,php-fpm
, Let's encrypt, Nginx directives, Reverse Proxy, Configure HTTP redirection Nginx, Return,proxy_pass (Reverse proxy)
,ngx_http_rewrite_module
,/etc/nginx/sites-enabled/
,error.log
,access.log
,/nginx status
, AIO
Advertising: