Bug description

~ 🏎  $ istioctl version
2019-11-15T14:48:41.027389Z	warn	will use `--remote=false` to retrieve version info due to `no Istio pods in namespace "istio-system"`
1.4.0

Expected behavior

Steps to reproduce the bug
Run istioctl version on a cluster which does not have istio installed

**Version (include the output of istioctl version --remote and `kubectl vers

Describe the bug
In https://www.getambassador.io/reference/core/ambassador/#lua-scripts-lua_scripts
the URL for "Envoy Lua filter documentation" leads to a 404. The URL is missing a "/http/" segment in the middle of the path. The correct URL should be:

https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/lua_filter

Docs will render fine locally without layouts/shortcodes/versioned_link_path.html https://github.com/solo-io/hugo-theme-soloio#examples-1 , but may be invalid once published to the live site.

We need some kind of validation to ensure we never publish docs with broken links

Issue description

in apisix.lua

in plugin.lua

is something wrong ? @membphis

Environment

• apisix version (cmd: apisix version):
• OS:

Minimal tes

Would there be any appetite to add a rule that checks for the inclusion of required and optional fields in your API?

Hey guys,

I just wanted to try out kanali on a fresh kubernetes cluster:

kubectl apply -f kanali/hack/helm-rbac.yaml

However I get following error message:

serviceaccount "tiller" created
Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply
clusterrolebinding.rbac.authorization.k8s.io "tiller" created
Error from

When I execute

kubectl apply -f samples/apigee/definitions

I got the following error.

customresourcedefinition. "apigees.config.istio.io" created
customresourcedefinition. "analytics.config.istio.io" created
authorization.config.istio.io "apigee" created
error: unable to recognize "samples/apigee/definitions.yaml": no matches for kind "analytics" in version "config.istio

Describe the bug
When adding a description to a path parameter, header, or query parameter in design view, the field displays improperly and cannot be used.

To Reproduce

1. Create a Path Parameter, Header, or Query Parameter in design view
2. Add a description by clicking the book icon

Expected behavior
A field appears that allows you to add a description.

**Screensh