Summary

Currently Kong supports writing configuration in a file, in YAML or JSON.
To provide a more flexible configuration, especially for those running Kong in different environments (dev, staging, production), an option to write configuration in lua can be very useful.

Additional Details

There are many use-cases that come to mind:

• Using environment variables inside the d

Currently at 43.2%.

Please answer these questions before submitting your issue.

• Why do you submit this issue?
  I want to use skywaling with brpc-java.
  https://github.com/baidu/brpc-java

• Question or discussion
  discussion

• Bug
  no

• Requirement
  yes

• Feature or performance improvement
  Feature

Question

• What do you want to know?

Bug

• Which version of SkyW

Issue Description

Type: bug report

Describe what happened

java.lang.IllegalStateException: failed to req API:/nacos/v1/ns/instance/beat after all servers([minion-register:8848]) tried: failed to req API:minion-register:8848/nacos/v1/ns/instance/beat. code:400 msg: java.lang.IllegalArgumentException: dom name can only have these characters: 0-9a-zA-Z-._:, current: DEFAULT_GROU

Bug Report

What is the issue?

I'm using kubens to quickly switch the default namespace that kubectl uses. This works by rewriting the current context in ~/.kube/config. For example, executing kubens ingress-nginx means that kubectl get pod nginx-ingress-controller-84dd6b84fd-gcb6x picks up the pod from the ingress-nginx namespace without

• Feature request

Expose stats scoped by the caller service, so linkerd can be used as the source of truth for all service to service call metrics.
Considering this can explode easily, it is probably better so expose only a limited numbers of stats.

For each route i would suggest to expose the same metrics exposed by https://github.com/twitter/finagle/blob/master/finagle-http/src/main/

In README.md there is the following command:

docker run --it  --name tgr -p 5000:5000 -e CLIENT_ID="xxxxxxx" -e CLIENT_SECRET="xxxxxxxxxxxxxxx" -e DEBUG="True" tgr

There is two issues with that:

1. It should be -it, rather than --it, since the first one is invalid
2. You also need to specify -e HOST="0.0.0.0" and -e PORT="5000" in order for the app to start.

Addi

Most of the headings on the website have anchor link targets, but it's awkward to actually get a link to them. Add anchor.js or something equivalent so there is clickable page element that can be used to obtain a link to an anchored element.

The New Feature

In the specified time range, if the number of errors exceeds the threshold, it is unavailable in the specified time range

Your scenes

Passive health check, remove abnormal services for a period of time

There's a non-deterministic test in client_factory_test.go that sometimes fail. Most of the time it seems ok, so it hasn't harmed so much and would be low priority at first glance... but it would be nice to see if there's a better way to write that.

Incriminated code line 54 I think:

time.Sleep(time.Millisecond * 100)

Example of failure: https://travis-ci.org/github/kiali/ki

Summary

The initial implementation is missing the following features:

1. %START_TIME% commands ignore the user-defined format string
2. %DYNAMIC_METADATA(NAMESPACE:KEY*):Z% commands return a stub value
3. %FILTER_STATE(KEY):Z% commands return a stub value

Proposal

At some point, Maesh will experience security issues. To handle them gracefully, we should document our security policy and define, at least:

• How and where security vulnerabilities will be reported.
• How to disclose a security vulnerability responsibly.

We should have a look at the GitHub [Security policy](https://help.github.com/en/github/managing-security-vulnerabiliti

When I visit http://www.servicemesher.com/istio-handbook,
the navigation links on the page left are invalid with 404 error.

All links have lost the /istio-handbook prefix.

Describe the bug
Our example uses aws ecr get-login for authentication. However in the AWS CLI version 2 aws ecr get-login is deprecated and is replaced with the command aws aws ecr get-login-password command. Hence the examples will fail if run on aws cli version 2.

Platform
All.

Additional context
The examples will continue to run using aws cli version 1.
Refer [here](htt

$ curl -X POST -vvvv  http://127.0.0.1:9989/shutdown
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to 127.0.0.1 (127.0.0.1) port 9989 (#0)
> POST /shutdown HTTP/1.1
> Host: 127.0.0.1:9989
> User-Agent: curl/7.52.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Length: 0
< Date: Tue, 11 Jul 2017 22:50:51 GMT
<
* Curl_http_done: called premature == 0
* Connection #0 to host 1

SMI spec should document the spec in detail - documenting fields in the spec.

Currently, the documentation is not documenting the exact specification of the fields in the spec. The approach currently followed is to describe the spec from an example, which does not cover all possibilities.

For ex. consider the following spec:

apiVersion: metrics.smi-spec.io/v1alpha1
kind: TrafficMetric

Describe the bug

istio-sidecar-injector is stick in ContianerCreating for fresh install of Istio v1.5.1.

$ kubectl get pods

istio-citadel-65cf6795c8-tcgp2            0/1     CrashLoopBackOff    249        20h
istio-egressgateway-5b6cb5c5-xwsrn        0/1     Running             0          20h
istio-ingressgateway-755776c4fb-24xcw     0/1     Running             0          20h

Motivation

We need to check the case of the remote connection of kernerl-forwarder and vppagent-forwarder via vxlan remote mechanism.

Test steps

1. Deploy nsmgr on node1. //force select vxlan remote mechanism
2. Deploy vppagent-forwarder on node1.
3. Deploy nsmgr on node2. //force select vxlan remote mechanism
4. Deploy kernel-forwarder on node2.
5. Deploy nse1 on node2