replace-response VS kubernetes-ingress

> But there are many scenarios where being able to extend the HTTP server via Lua is more convenient than writing a plugin I would think?

Well, Caddy is written in Go, so it's only natural to write a plugin in Go. Statically compiled into your binary. We provide a tool called `xcaddy` which is used to produce builds of Caddy with any plugins you need. You just need Go installed on your system to run it, no other dependencies.

The reason why Lua is used for OpenResty is because writing plugins in C is... not fun.

You can absolutely do what you described with an HTTP handler module in Caddy. You'd just wrap the req.Body with a reader that watches the bytes as they're copied through the stream, and when you see the part you want to log, you do that.

We have a replace-response plugin which takes a similar approach, except it manipulates the response as it's being streamed back to the client. https://github.com/caddyserver/replace-response The whole plugin is just one file of Go code.

Everything in the YAML snippets below — except for ingress configuration — relates to configuring the NGINX ingress controller. This includes customizing the default configuration.

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.

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 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

The example below shows how to configure a canary deployment using Nginx Ingress. The custom annotations used here are specific to Nginx:

This: https://kubernetes.github.io/ingress-nginx/ Not this: https://docs.nginx.com/nginx-ingress-controller/

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.

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!

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