kubernetes-ingress
njs
Our great sponsors
kubernetes-ingress | njs | |
---|---|---|
28 | 3 | |
4,526 | 733 | |
0.9% | 0.5% | |
9.8 | 9.2 | |
7 days ago | 4 days ago | |
Go | C | |
Apache License 2.0 | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kubernetes-ingress
-
☸️ Kubernetes NGINX Ingress Controller: 10+ Complementary Configurations for Web Applications
Everything in the YAML snippets below — except for ingress configuration — relates to configuring the NGINX ingress controller. This includes customizing the default configuration.
-
Breaking Terraform files into composable layers
In these examples, I assume that users have deployed an nginx-ingress-controller to their cluster through the eks layer. This controller is responsible for creating an nlb and exposing Elasticsearch and Kibana to the internet through their ingresses.
-
Implementing TLS in Kubernetes
Now, you need to install the Nginx Ingress Controller so that it can redirect incoming requests to your payment app to use HTTPS. Since you've exposed the app using nodePort, you need to install the Ingress using a custom value file that specifies the service type to NodePort.
-
Kubernetes cannot upload files larger than 1MB
Kubernetes We have a kubernetes cluster which has a dropwizard based web application running as a service. This application has a rest uri to upload files. It cannot upload files larger than 1MB. I get the following error: ERROR [2017-07-27 13:32:47,629] io.dropwizard.jersey.errors.LoggingExceptionMapper: Error handling a request: ea812501b414f0d9! com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')! at [Source: ! 413 Request Entity Too Large! ! 413 Request Entity Too Large! nginx/1.11.3! ! Hide resultsI have tried the suggestions given in https://github.com/nginxinc/kubernetes-ingress/issues/21. I have edited the Ingress to set the proxy-body-size annotation. Also, I have tried using the configMap without any success. we are using kubernetes version 1.5. Please let me know if you need additional information. Answer link : https://codehunter.cc/a/kubernetes/kubernetes-cannot-upload-files-larger-than-1mb
-
A Comprehensive Guide to API Gateways, Kubernetes Gateways, and Service Meshes
The example below shows how to configure a canary deployment using Nginx Ingress. The custom annotations used here are specific to Nginx:
-
Ingress controller for vanilla k8s
This: https://kubernetes.github.io/ingress-nginx/ Not this: https://docs.nginx.com/nginx-ingress-controller/
-
Assign an External IP to a Node
So far, i've been following the example here to set up an nginx Ingress Controller and some test services behind it. However, I am unable to follow Step 6 which displays the external IP for the node that the load balancer is running on as my node does not have an ExternalIP in the addresses section, only a LegacyHostIP and InternalIP.
- List of template objects & properties to use with templates?
-
How to use ACM public certificate for Nginx ingress controller?
Also, of personal note, I highly recommend you use the "ingress-nginx" controller which has a huge community and is of much higher quality and flexibility than the "nginx-ingress controller by nginx inc". I've had a lot of success with dozens of clients with this controller. It rocks!
-
Questions about Blue/Green & Canary Deployments (Vanilla K8)
For example, the ingress project from NGINX has its own CRDs that give better control over service versions and blue/green and canary cutovers https://github.com/nginxinc/kubernetes-ingress/tree/v3.0.0/examples/custom-resources/traffic-splitting
njs
-
The Future of Nginx: Getting Back to Our Open Source Roots
This article came at an interesting timing for me, since I recently started to explore building my own CDN node on top of NGINX open source inspired by this article from Fly: https://fly.io/blog/the-5-hour-content-delivery-network/
I've worked with nginx in the past, and didn't have a great experience, so I was apprehensive diving in, but this time was very different. I think njs (their custom JS scripting environment) was a game changer. Support is built in to nginx core, and available by default in their docker containers, so it's much easier to get started with than Lua scripting. Their JS feature support has some quirks (no optional chaining, array destructuring, console.log's don't show up in logs, are some examples of things that threw me off) but overall nothing that blocked me from implementing the functionality I needed, and the integration points within the nginx config felt fairly natural.
I did run into a number of things that were locked behind their commercial offering that made me a bit uncomfortable betting on it for the long term compared to purely open source alternatives. Off the top of my head:
- DNS discovery. There's a thread on the Fly example repo accompanying the blog post that describes the use case and proposes some workarounds: https://github.com/fly-apps/nginx-cluster/issues/2. Life would be a lot simpler if DNS discovery from the commercial offering was just available (i.e. we can outright delete a brittle bash script that makes DNS queries and reloads nginx on a 5 second interval). This was mentioned in the article as something they're planning to open source.
- Access to some kind of shared key-value store for custom caching logic in njs scripts. With Lua we could just connect to Redis, but njs can't seem to establish persistent network connections for now, so that's off the table. This wasn't mentioned in the article, but they did mention in this Github issue that they're planning on open sourcing their keyval module for this use case: https://github.com/nginx/njs/issues/437. I have some use cases where being able to connect to Redis would be ideal, since syncing keyval across a cluster seems to be eventually consistent (https://docs.nginx.com/nginx/admin-guide/high-availability/z...), but for most of my caching use cases it should be sufficient.
So this article, along with their overall willingness to work with the community to identify and bring commercial features into open source (at least from what I've observed across their responses to Github issues) does a lot to alleviate those concerns.
Though at the end of the day, I don't necessarily need every nginx feature to be in open source. I have no problems with paying for great software like nginx to support its development. But as a small bootstrapped founder, their current pricing structure (from what I could gather on the internet is ~ 2k-5k per running instance), is completely prohibitive. It'd probably require a revamp to the way they sell the software (i.e. self-serve onboarding and automatic license provisioning for smaller customers instead of having customers of all sizes go through expensive sales people), but I'd love to see a more progressive pricing structure with a lower barrier to entry for their commercial product.
-
ngx_stream_js_module: ngx.fetch in js_filter function
I'd leave guys a bug at github: https://github.com/nginx/njs .
- Nginx JavaScript in Your Web Server Configuration
What are some alternatives?
amicontained - Container introspection tool. Find out what container runtime is being used as well as features available.
lua-nginx-module - Embed the Power of Lua into NGINX HTTP servers
ingress-nginx - Ingress-NGINX Controller for Kubernetes
server-side-tls - Server side TLS Tools
application-gateway-kubernetes-ingress - This is an ingress controller that can be run on Azure Kubernetes Service (AKS) to allow an Azure Application Gateway to act as the ingress for an AKS cluster.
nginx-cluster - A horizontally scalable NGINX caching cluster
ingress - Ingress-NGINX Controller for Kubernetes [Moved to: https://github.com/kubernetes/ingress-nginx]
cache-handler - Distributed HTTP caching module for Caddy
docker-swarm-ingress - Nginx swarm ingress controller, a minimalistic approach to allow routing into a Docker Swarm based on the public hostnames.
replace-response - Caddy module that performs replacements in response bodies
traefik - The Cloud Native Application Proxy [Moved to: https://github.com/traefik/traefik]
caddy-l4 - Layer 4 (TCP/UDP) app for Caddy