| sidebar_label | title | description | hide_table_of_contents | type | category | sidebar_class_name | logoUrl | tags | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Nginx |
Nginx |
Nginx Ingress pack in Spectro Cloud |
true |
integration |
|
hide-from-sidebar |
|
Integration creates the following components:
- Ingress Controller.
- Default Backend.
NGINX Ingress controller provides an option to set a default SSL certificate to be used for requests that do not match any of the configured server names. The default certificate will also be used for ingress tls: sections that do not have a secretName option. Below steps will come in handy to set the default certificate.
- Create a secret with key and certificate
kubectl -n kube-system create secret tls ingress-tls --cert server.crt --key server.key
- Edit Nginx ingress pack values to include extraArgs.default-ssl-certificate section which will reference the secret
created above
charts: nginx-ingress: fullnameOverride: "nginx-ingress" controller: ... ... extraArgs: default-ssl-certificate: "kube-system/ingress-tls"
Integration creates the following components:
- Ingress Controller.
- Default Backend.
NGINX Ingress controller provides an option to set a default SSL certificate to be used for requests that do not match any of the configured server names. The default certificate will also be used for ingress tls: sections that do not have a secretName option. Below steps will come in handy to set the default certificate.
- Create a secret with key and certificate
kubectl -n kube-system create secret tls ingress-tls --cert server.crt --key server.key
- Edit Nginx ingress pack values to include extraArgs.default-ssl-certificate section which will reference the secret
created above
charts: nginx-ingress: fullnameOverride: "nginx-ingress" controller: ... ... extraArgs: default-ssl-certificate: "kube-system/ingress-tls"
Integration creates the following components:
- Ingress Controller.
- Default Backend.
NGINX Ingress controller provides an option to set a default SSL certificate to be used for requests that do not match any of the configured server names. The default certificate will also be used for ingress tls: sections that do not have a secretName option. Below steps will come in handy to set the default certificate.
- Create a secret with key and certificate
kubectl -n kube-system create secret tls ingress-tls --cert server.crt --key server.key
- Edit Nginx ingress pack values to include extraArgs.default-ssl-certificate section which will reference the secret
created above
charts: nginx-ingress: fullnameOverride: "nginx-ingress" controller: ... ... extraArgs: default-ssl-certificate: "kube-system/ingress-tls"
Integration creates the following components:
- Ingress Controller.
- Default Backend.
NGINX Ingress controller provides an option to set a default SSL certificate to be used for requests that do not match any of the configured server names. The default certificate will also be used for ingress tls: sections that do not have a secretName option. Below steps will come in handy to set the default certificate.
- Create a secret with key and certificate
kubectl -n kube-system create secret tls ingress-tls --cert server.crt --key server.key
- Edit Nginx ingress pack values to include extraArgs.default-ssl-certificate section which will reference the secret
created above
charts: nginx-ingress: fullnameOverride: "nginx-ingress" controller: ... ... extraArgs: default-ssl-certificate: "kube-system/ingress-tls"
Integration creates the following components:
- Ingress Controller.
- Default Backend.
NGINX Ingress controller provides an option to set a default SSL certificate to be used for requests that do not match any of the configured server names. The default certificate will also be used for ingress tls: sections that do not have a secretName option. Below steps will come in handy to set the default certificate.
- Create a secret with key and certificate
kubectl -n kube-system create secret tls ingress-tls --cert server.crt --key server.key
- Edit Nginx ingress pack values to include extraArgs.default-ssl-certificate section which will reference the secret
created above
charts: nginx-ingress: fullnameOverride: "nginx-ingress" controller: ... ... extraArgs: default-ssl-certificate: "kube-system/ingress-tls"
Integration creates the following components:
- Ingress Controller.
- Default Backend.
NGINX Ingress controller provides an option to set a default SSL certificate to be used for requests that do not match any of the configured server names. The default certificate will also be used for ingress tls: sections that do not have a secretName option. Below steps will come in handy to set the default certificate.
- Create a secret with key and certificate
kubectl -n kube-system create secret tls ingress-tls --cert server.crt --key server.key
- Edit Nginx ingress pack values to include extraArgs.default-ssl-certificate section which will reference the secret
created above
charts: nginx-ingress: fullnameOverride: "nginx-ingress" controller: ... ... extraArgs: default-ssl-certificate: "kube-system/ingress-tls"
You can reference the nginx pack in Terraform with the following data resource.
data "spectrocloud_registry" "public_registry" {
name = "Public Repo"
}
data "spectrocloud_pack" "nginx" {
name = "nginx"
version = "1.10.0"
registry_uid = data.spectrocloud_registry.public_registry.id
}