Add Krakend image

Signed-off-by: Albert Lombarte <[email protected]>

Author: alombarte

krakend/content.md

@@ -4,13 +4,13 @@
 
 [KrakenD](https://www.krakend.io/) is a stateless, high-performance, enterprise-ready, open-source API gateway written in Go. Its engine (formerly known as *KrakenD Framework*) is now a **Linux Foundation Project** codenamed [Lura Project](https://luraproject.org/). Lura is the only enterprise-grade API Gateway hosted in a neutral, open forum.
 
-KrakenD is lightweight and straightforward as it only requires writing the configuration file. No Go knowledge is required. It offers connectivity to internal and external services, transformation and filtering of data, aggregation of multiple data sources (APIs, gRPC, queues and pub/sub, lambda, etc) simultaneously or in cascade, protects the access to your API, throughputs its usage, and integrates with a lot of third-parties.
+KrakenD is lightweight and straightforward, as it only requires writing the configuration file. No Go knowledge is required. It offers connectivity to internal and external services, data transformation and filtering, and aggregation of multiple data sources (APIs, gRPC, queues and pub/sub, lambda, etc.) simultaneously or in cascade. It protects access to your API, throughputs its usage, and integrates with many third-parties.
 
 All features are designed to offer extraordinary performance and infinite scalability.
 
 ## How to use this image
 
-KrakenD only needs a single configuration file to create an API Gateway, although you can have a complex setup reflecting your organization structure. The configuration file(s) can live anywhere in the container, but the default location is `/etc/krakend`.
+KrakenD only needs a single configuration file to create an API Gateway, although you can have a complex setup reflecting your organization structure. The configuration file(s) can live anywhere in the container, but the default location (the workdir) is `/etc/krakend`.
 
 To use the image, `COPY` your `krakend.json` file inside the container or mount it using a volume. The configuration is checked only once during the startup and never used again. Don't have a config file yet? Generate it with the [KrakenD Designer UI](https://designer.krakend.io).
 
@@ -20,10 +20,10 @@ To use the image, `COPY` your `krakend.json` file inside the container or mount
 
 You can start an empty gateway with a health check with the following commands:
 
-```console
-$ docker run -d -p 8080:8080 -v "$PWD:/etc/krakend/" %%IMAGE%%
-...
-$ curl http://localhost:8080/__health
+```bash
+docker run -d -p 8080:8080 -v "$PWD:/etc/krakend/" %%IMAGE%%
+
+curl http://localhost:8080/__health
 {"agents":{},"now":"2024-05-23 14:35:55.552591448 +0000 UTC m=+26.856583003","status":"ok"}
 ```
 
@@ -37,21 +37,23 @@ The configuration files are taken from the current directory (`$PWD`). Therefore
 
 This flag is **SAFE to use in production**. It's meant to enable KrakenD as a fake backend itself by enabling a [`/__debug` endpoint](https://www.krakend.io/docs/endpoints/debug-endpoint/)
 
-```console
-    docker run -p 8080:8080 -v "${PWD}:/etc/krakend/" %%IMAGE%% run -d -c /etc/krakend/krakend.json
+```bash
+docker run -p 8080:8080 -v "${PWD}:/etc/krakend/" %%IMAGE%% run -d -c /etc/krakend/krakend.json
 ```
 
 #### Checking the syntax of your configuration file
 
 See the [check command](https://www.krakend.io/docs/commands/check/)
 
-```console
-    docker run -it -v $PWD:/etc/krakend/ %%IMAGE%% check --config krakend.json
+```bash
+docker run -it -v $PWD:/etc/krakend/ %%IMAGE%% check --config krakend.json
 ```
 
 #### Show the help:
 
-	docker run -it %%IMAGE%% help
+```bash
+docker run --rm -it %%IMAGE%% help
+```
 
 ### Building your custom KrakenD image
 
@@ -63,10 +65,10 @@ Your `Dockerfile` could look like this:
 FROM %%IMAGE%%:<version>
 # NOTE: Avoid using :latest image on production. Stick to a major version instead.
 
-COPY krakend.json /etc/krakend/krakend.json
+COPY krakend.json ./
 
 # Check and test that the file is valid
-RUN krakend check -d -t -c /etc/krakend/krakend.json
+RUN krakend check -t --lint-no-network -c krakend.json
 ```
 
 If you want to manage your KrakenD configuration using multiple files and folders, reusing templates, and distributing the configuration amongst your teams, you can use the [flexible configuration (FC)](https://www.krakend.io/docs/configuration/flexible-config/). The following `Dockerfile` combines FC, the `krakend check` command, and a 2-step build.
@@ -142,9 +144,11 @@ services:
 
 ### Container permissions and commands
 
-All `krakend` commands are executed as `krakend` user (uid=1000) through `su-exec`, and the rest of the commands (e.g., `sh`) are executed as root.
+All `krakend` commands are executed as `krakend` user (uid=1000), and the rest of the commands (e.g., `sh`) are executed as root.
 
-You can directly use sub-commands of `krakend` like `run`, `help`, `version`, `check`, `check-plugin` or `validate` as the entrypoint will add the `krakend` command automatically. For example, the following lines are equivalent:
+You can directly use sub-commands of `krakend` like `run`, `help`, `version`, `check`, `check-plugin`, or `test-plugin` as the entrypoint will add the `krakend` command automatically. For example, the following lines are equivalent:
 
-	docker run -it %%IMAGE%% help
-	docker run -it %%IMAGE%% krakend help
+```bash
+docker run --rm -it %%IMAGE%% help
+docker run --rm -it %%IMAGE%% krakend help
+```