![]() ![]() Requires ’error-log-level: debug’ in the ConfigMap. If a ConfigMap is set, but the Ingress Controller is not able to fetch it from Kubernetes API, the Ingress Controller will fail to start.Įnable debugging for NGINX. Default for NGINX Plus is .Ī ConfigMap resource for customizing NGINX configuration.Path to the main NGINX configuration template. When logging hits line file:N, emit a stack trace. Specifies the name of the ConfigMap, within the same namespace as the controller, used as the lock for leader election. Default for NGINX is default for NGINX Plus is. Path to the ingress NGINX configuration template for an ingress resource. The Ingress Controller processes all the resources that do not have the ingressClassName field. have the ingressClassName field resource equal to the class. The Ingress Controller only processes resources that belong to its class - i.e. Otherwise, the Ingress Controller will fail to start. ![]() (default /nginx-health)Ī corresponding IngressClass resource with the name equal to the class must be deployed. Sets the URI of health status location in the default server. Useful for external health-checking of the Ingress Controller. The location responds with the 200 status code for any request. The IP of the BIG-IP system is used when reporting the status of Ingress, VirtualServer and VirtualServerRoute resources.Ī GlobalConfiguration resource for global configuration of the Ingress Controller.Īdds a location “/nginx-health” to the default server. Specifies the name of the IngressLink resource, which exposes the Ingress Controller pods via a BIG-IP system. The external address of the service is used when reporting the status of Ingress, VirtualServer and VirtualServerRoute resources.įor Ingress resources only: Requires -report-ingress-status. Specifies the name of the service with the type LoadBalancer through which the Ingress Controller pods are exposed externally. enable-leader-electionĮnables Leader election to avoid multiple replicas of the controller reporting the status of Ingress, VirtualServer and VirtualServerRoute resources – only one replica will report status.Įnable x509 automated certificate management for VirtualServer resources using cert-manager (cert-manager.io).Įnable integration with ExternalDNS for configuring public DNS entries for VirtualServer resources using ExternalDNS. NOTE: This flag will be removed in release 2.7 and the year will be included by default. To enable OIDC Policies please use -enable-oidc instead. If the argument is set, but the Ingress Controller is not able to fetch the Secret from Kubernetes API, the Ingress Controller will fail to start.Įnables preview policies. If the argument is not set, for such Ingress/VirtualServer hosts NGINX will break any attempt to establish a TLS connection. If a secret is set, but the Ingress Controller is not able to fetch it from Kubernetes API, or it is not set and the Ingress Controller fails to read the file “/etc/nginx/secrets/default”, the Ingress Controller will fail to start.Ī Secret with a TLS certificate and key for TLS termination of every Ingress/VirtualServer host for which TLS termination is enabled but the Secret is not specified.If /etc/nginx/secrets/default doesn’t exist, the Ingress Controller will configure NGINX to reject TLS connections to the default server.If not set, certificate and key in the file /etc/nginx/secrets/default are used.Secret with a TLS certificate and key for TLS termination of the default server. See the Installation with Helm doc.īelow we describe the available command-line arguments:Įnable custom NGINX configuration snippets in Ingress, VirtualServer, VirtualServerRoute and TransportServer resources. If you’re using Helm to install the Ingress Controller, modify the parameters of the Helm chart that correspond to the command-line arguments.If you’re using Kubernetes manifests (Deployment or DaemonSet) to install the Ingress Controller, to set the command-line arguments, modify those manifests accordingly.Setting the arguments depends on how you install the Ingress Controller: The Ingress Controller supports several command-line arguments.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |