helm install stable/kong --name kong --namespace kong --values https://bit.ly/2RgSRio --version 0.9.0
To check status: watch -n 1 kubectl get pod -n kong
#!/bin/bash | |
set -o errexit | |
############################################################## | |
# Make sure you have the dependencies for building OpenResty # | |
############################################################## | |
BUILD_DIR=/tmp | |
OPENRESTY_VERSION=1.7.10.2rc0 |
We are happy to announce the release of Kuma 0.4! This is a major release focused on significantly better observability capabilities, that also includes many new features and improvements across the board.
This release also marks the 10th release of Kuma since September 2019! We are very proud of the release momentum we have executed so far, and we are looking forward to accelerating the delivery of more advanced L7 features within the next few months, as well as more advanced networking support for more complex Service Mesh deployments across hybrid environments.
$.ajax({ | |
url: 'MASHAPE-URL', // The URL to the API. You can get this by clicking on "Show CURL example" from an API profile | |
type: 'POST', // The HTTP Method | |
data: {}, // Additional parameters here | |
dataType: 'json', | |
success: function(data) { alert(JSON.stringify(data)); }, | |
error: function(err) { alert(err); }, | |
beforeSend: function(xhr) { | |
xhr.setRequestHeader("X-Mashape-Authorization", "YOUR-MASHAPE-KEY"); // Enter here your Mashape key | |
} |
#!/bin/bash | |
set -o errexit | |
OPENRESTY_VERSION=1.7.10.2rc0 | |
OPENSSL_VERSION=1.0.2a | |
OPENRESTY_CONFIGURE_PARAMS="" | |
# Preparing environment | |
DIR=$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd ) | |
echo "Current directory is: "$DIR |
$ make | |
/Users/marco/work/bin/gox | |
? github.com/hashicorp/serf/client [no test files] | |
ok github.com/hashicorp/serf/cmd/serf 0.015s | |
2016/10/25 14:11:51 [INFO] agent: Serf agent starting | |
2016/10/25 14:11:51 [INFO] serf: EventMemberJoin: 127.0.0.10 127.0.0.10 | |
2016/10/25 14:11:51 [INFO] agent: Serf agent starting | |
2016/10/25 14:11:51 [INFO] serf: EventMemberJoin: 127.0.0.11 127.0.0.11 | |
2016/10/25 14:11:51 [INFO] agent: Received event: member-join | |
2016/10/25 14:11:51 [INFO] agent: Received event: member-join |
echo "CIAO" |
This document is a logical reasoning that takes elements from our meetings, a brainstorming that evolves from the beginnign to the end. Don't make any assumptions until you reach the end. Because the argument is very complex, it incrementally address the whole picture step by step.
This Gist comes from the realization that plugin mappings can also be adapted to consumers, and that grouping and filters would be available for both consumers and plugin configurations.
It specifically covers the topic of plugin and consumer mapping from the user's perspective, thus the interface and not the internals.
Let's suppose that by default every consumer can consume any API:
Kong 0.6.0 introduces Clustering and a new in-memory core cache invalidation strategy which dramatically improves the performance of the system. The following benchmark measures the in-memory caching improvements of Kong 0.6.0 compared to the previous Kong 0.5.4 which still uses the old time-based expiration strategy.
The test involves consuming an API running on a separate machine, that returns a simple 200 OK
JSON response with the following body:
{"message": "hello world"}