diff --git a/app/_data/docs_nav_ce_0.13.x.yml b/app/_data/docs_nav_ce_0.13.x.yml index 6dd16f467faf..0353c9a52c70 100644 --- a/app/_data/docs_nav_ce_0.13.x.yml +++ b/app/_data/docs_nav_ce_0.13.x.yml @@ -246,7 +246,7 @@ url: /admin-api/#delete-sni - text: Upstream Object routes - url: /admin-api/#upstream-objects + url: /admin-api/#upstream-object items: - text: Add Upstream url: /admin-api/#add-upstream diff --git a/app/_data/docs_nav_ce_0.14.x.yml b/app/_data/docs_nav_ce_0.14.x.yml index 4cd6289dc09a..0903030b4ccd 100644 --- a/app/_data/docs_nav_ce_0.14.x.yml +++ b/app/_data/docs_nav_ce_0.14.x.yml @@ -266,7 +266,7 @@ url: /admin-api/#delete-sni - text: Upstream Object routes - url: /admin-api/#upstream-objects + url: /admin-api/#upstream-object items: - text: Add Upstream url: /admin-api/#add-upstream diff --git a/app/_data/docs_nav_ce_1.0.x.yml b/app/_data/docs_nav_ce_1.0.x.yml index 71909ed5cdc0..970494796253 100644 --- a/app/_data/docs_nav_ce_1.0.x.yml +++ b/app/_data/docs_nav_ce_1.0.x.yml @@ -275,7 +275,7 @@ url: /admin-api/#delete-sni - text: Upstream Object routes - url: /admin-api/#upstream-objects + url: /admin-api/#upstream-object items: - text: Add Upstream url: /admin-api/#add-upstream diff --git a/app/_data/docs_nav_ce_1.1.x.yml b/app/_data/docs_nav_ce_1.1.x.yml index b485d98c0bb0..c8b992891ede 100644 --- a/app/_data/docs_nav_ce_1.1.x.yml +++ b/app/_data/docs_nav_ce_1.1.x.yml @@ -281,7 +281,7 @@ url: /admin-api/#delete-sni - text: Upstream Object routes - url: /admin-api/#upstream-objects + url: /admin-api/#upstream-object items: - text: Add Upstream url: /admin-api/#add-upstream diff --git a/app/_data/docs_nav_ee_0.34-x.yml b/app/_data/docs_nav_ee_0.34-x.yml index bd6bb88a88b6..456546519073 100644 --- a/app/_data/docs_nav_ee_0.34-x.yml +++ b/app/_data/docs_nav_ee_0.34-x.yml @@ -67,7 +67,7 @@ - text: SNI Object url: /admin-api/#sni-objects - text: Upstream Object - url: /admin-api/#upstream-objects + url: /admin-api/#upstream-object - text: Target Object url: /admin-api/#target-object diff --git a/app/_data/docs_nav_ee_0.35-x.yml b/app/_data/docs_nav_ee_0.35-x.yml index acff2d428273..4859f1724a4f 100644 --- a/app/_data/docs_nav_ee_0.35-x.yml +++ b/app/_data/docs_nav_ee_0.35-x.yml @@ -144,7 +144,7 @@ - text: SNI Object routes url: /admin-api/#sni-objects - text: Upstream Object routes - url: /admin-api/#upstream-objects + url: /admin-api/#upstream-object - text: Target Object routes url: /admin-api/#target-object - text: Workspace Object routes diff --git a/app/enterprise/0.34-x/health-checks-circuit-breakers.md b/app/enterprise/0.34-x/health-checks-circuit-breakers.md index 0d401a1ac11b..85deb42e357a 100644 --- a/app/enterprise/0.34-x/health-checks-circuit-breakers.md +++ b/app/enterprise/0.34-x/health-checks-circuit-breakers.md @@ -198,7 +198,7 @@ unhealthy status to a non-zero interval. ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -291,6 +291,6 @@ upstreams. [targetobject]: /enterprise/{{page.kong_version}}/admin-api#target-object [addupstream]: /enterprise/{{page.kong_version}}/admin-api#add-upstream [clustering]: /enterprise/{{page.kong_version}}/clustering -[upstreamobjects]: /enterprise/{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /enterprise/{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /enterprise/{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /enterprise/{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/enterprise/0.35-x/health-checks-circuit-breakers.md b/app/enterprise/0.35-x/health-checks-circuit-breakers.md index 6e60733c2fdd..555d9a145aea 100644 --- a/app/enterprise/0.35-x/health-checks-circuit-breakers.md +++ b/app/enterprise/0.35-x/health-checks-circuit-breakers.md @@ -204,7 +204,7 @@ active health checks on `healthy` status to zero, and active checks on ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -318,6 +318,6 @@ upstreams. [targetobject]: /enterprise/{{page.kong_version}}/admin-api#target-object [addupstream]: /enterprise/{{page.kong_version}}/admin-api#add-upstream [clustering]: /enterprise/{{page.kong_version}}/clustering -[upstreamobjects]: /enterprise/{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /enterprise/{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /enterprise/{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /enterprise/{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/enterprise/0.36-x/health-checks-circuit-breakers.md b/app/enterprise/0.36-x/health-checks-circuit-breakers.md index bc955cefe0c2..cd72d3d4e658 100644 --- a/app/enterprise/0.36-x/health-checks-circuit-breakers.md +++ b/app/enterprise/0.36-x/health-checks-circuit-breakers.md @@ -204,7 +204,7 @@ unhealthy status to a non-zero interval. ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -318,6 +318,6 @@ upstreams. [targetobject]: /enterprise/{{page.kong_version}}/admin-api#target-object [addupstream]: /enterprise/{{page.kong_version}}/admin-api#add-upstream [clustering]: /enterprise/{{page.kong_version}}/clustering -[upstreamobjects]: /enterprise/{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /enterprise/{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /enterprise/{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /enterprise/{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/enterprise/1.3-x/health-checks-circuit-breakers.md b/app/enterprise/1.3-x/health-checks-circuit-breakers.md index 9a9aef4f09c0..8355a2c471c3 100644 --- a/app/enterprise/1.3-x/health-checks-circuit-breakers.md +++ b/app/enterprise/1.3-x/health-checks-circuit-breakers.md @@ -245,7 +245,7 @@ active health checks on `healthy` status to zero, and active checks on ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -359,6 +359,6 @@ upstreams. [targetobject]: /enterprise/{{page.kong_version}}/admin-api#target-object [addupstream]: /enterprise/{{page.kong_version}}/admin-api#add-upstream [clustering]: /enterprise/{{page.kong_version}}/clustering -[upstreamobjects]: /enterprise/{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /enterprise/{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /enterprise/{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /enterprise/{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/enterprise/1.5.x/health-checks-circuit-breakers.md b/app/enterprise/1.5.x/health-checks-circuit-breakers.md index f71dd07cd360..b2d0fcc12f06 100644 --- a/app/enterprise/1.5.x/health-checks-circuit-breakers.md +++ b/app/enterprise/1.5.x/health-checks-circuit-breakers.md @@ -244,7 +244,7 @@ active health checks on `healthy` status to zero, and active checks on ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -358,6 +358,6 @@ upstreams. [targetobject]: /enterprise/{{page.kong_version}}/admin-api#target-object [addupstream]: /enterprise/{{page.kong_version}}/admin-api#add-upstream [clustering]: /enterprise/{{page.kong_version}}/clustering -[upstreamobjects]: /enterprise/{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /enterprise/{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /enterprise/{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /enterprise/{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/enterprise/2.1.x/health-checks-circuit-breakers.md b/app/enterprise/2.1.x/health-checks-circuit-breakers.md index fea41e0cfa0a..38c3520de3b2 100644 --- a/app/enterprise/2.1.x/health-checks-circuit-breakers.md +++ b/app/enterprise/2.1.x/health-checks-circuit-breakers.md @@ -242,7 +242,7 @@ active health checks on `healthy` status to zero, and active checks on ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -356,6 +356,6 @@ upstreams. [targetobject]: /enterprise/{{page.kong_version}}/admin-api#target-object [addupstream]: /enterprise/{{page.kong_version}}/admin-api#add-upstream [clustering]: /enterprise/{{page.kong_version}}/clustering -[upstreamobjects]: /enterprise/{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /enterprise/{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /enterprise/{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /enterprise/{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/enterprise/2.2.x/health-checks-circuit-breakers.md b/app/enterprise/2.2.x/health-checks-circuit-breakers.md index fea41e0cfa0a..38c3520de3b2 100644 --- a/app/enterprise/2.2.x/health-checks-circuit-breakers.md +++ b/app/enterprise/2.2.x/health-checks-circuit-breakers.md @@ -242,7 +242,7 @@ active health checks on `healthy` status to zero, and active checks on ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -356,6 +356,6 @@ upstreams. [targetobject]: /enterprise/{{page.kong_version}}/admin-api#target-object [addupstream]: /enterprise/{{page.kong_version}}/admin-api#add-upstream [clustering]: /enterprise/{{page.kong_version}}/clustering -[upstreamobjects]: /enterprise/{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /enterprise/{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /enterprise/{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /enterprise/{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/enterprise/2.3.x/health-checks-circuit-breakers.md b/app/enterprise/2.3.x/health-checks-circuit-breakers.md index fea41e0cfa0a..38c3520de3b2 100644 --- a/app/enterprise/2.3.x/health-checks-circuit-breakers.md +++ b/app/enterprise/2.3.x/health-checks-circuit-breakers.md @@ -242,7 +242,7 @@ active health checks on `healthy` status to zero, and active checks on ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -356,6 +356,6 @@ upstreams. [targetobject]: /enterprise/{{page.kong_version}}/admin-api#target-object [addupstream]: /enterprise/{{page.kong_version}}/admin-api#add-upstream [clustering]: /enterprise/{{page.kong_version}}/clustering -[upstreamobjects]: /enterprise/{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /enterprise/{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /enterprise/{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /enterprise/{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/enterprise/2.4.x/health-checks-circuit-breakers.md b/app/enterprise/2.4.x/health-checks-circuit-breakers.md index fea41e0cfa0a..38c3520de3b2 100644 --- a/app/enterprise/2.4.x/health-checks-circuit-breakers.md +++ b/app/enterprise/2.4.x/health-checks-circuit-breakers.md @@ -242,7 +242,7 @@ active health checks on `healthy` status to zero, and active checks on ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -356,6 +356,6 @@ upstreams. [targetobject]: /enterprise/{{page.kong_version}}/admin-api#target-object [addupstream]: /enterprise/{{page.kong_version}}/admin-api#add-upstream [clustering]: /enterprise/{{page.kong_version}}/clustering -[upstreamobjects]: /enterprise/{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /enterprise/{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /enterprise/{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /enterprise/{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/enterprise/2.5.x/health-checks-circuit-breakers.md b/app/enterprise/2.5.x/health-checks-circuit-breakers.md index fea41e0cfa0a..38c3520de3b2 100644 --- a/app/enterprise/2.5.x/health-checks-circuit-breakers.md +++ b/app/enterprise/2.5.x/health-checks-circuit-breakers.md @@ -242,7 +242,7 @@ active health checks on `healthy` status to zero, and active checks on ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -356,6 +356,6 @@ upstreams. [targetobject]: /enterprise/{{page.kong_version}}/admin-api#target-object [addupstream]: /enterprise/{{page.kong_version}}/admin-api#add-upstream [clustering]: /enterprise/{{page.kong_version}}/clustering -[upstreamobjects]: /enterprise/{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /enterprise/{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /enterprise/{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /enterprise/{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/gateway-oss/0.13.x/health-checks-circuit-breakers.md b/app/gateway-oss/0.13.x/health-checks-circuit-breakers.md index 834798aec960..e1356fcd3bf7 100644 --- a/app/gateway-oss/0.13.x/health-checks-circuit-breakers.md +++ b/app/gateway-oss/0.13.x/health-checks-circuit-breakers.md @@ -198,7 +198,7 @@ active health checks on `healthy` status to zero, and active checks on ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -291,6 +291,6 @@ upstreams. [targetobject]: /{{page.kong_version}}/admin-api#target-object [addupstream]: /{{page.kong_version}}/admin-api#add-upstream [clustering]: /{{page.kong_version}}/clustering -[upstreamobjects]: /{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/gateway-oss/0.14.x/health-checks-circuit-breakers.md b/app/gateway-oss/0.14.x/health-checks-circuit-breakers.md index 0eeabcb68236..bc815af26d2f 100644 --- a/app/gateway-oss/0.14.x/health-checks-circuit-breakers.md +++ b/app/gateway-oss/0.14.x/health-checks-circuit-breakers.md @@ -202,7 +202,7 @@ active health checks on `healthy` status to zero, and active checks on ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -299,6 +299,6 @@ upstreams. [targetobject]: /{{page.kong_version}}/admin-api#target-object [addupstream]: /{{page.kong_version}}/admin-api#add-upstream [clustering]: /{{page.kong_version}}/clustering -[upstreamobjects]: /{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/gateway-oss/1.0.x/health-checks-circuit-breakers.md b/app/gateway-oss/1.0.x/health-checks-circuit-breakers.md index 4c588b96de87..83ea4c66586f 100644 --- a/app/gateway-oss/1.0.x/health-checks-circuit-breakers.md +++ b/app/gateway-oss/1.0.x/health-checks-circuit-breakers.md @@ -204,7 +204,7 @@ active health checks on `healthy` status to zero, and active checks on ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -318,6 +318,6 @@ upstreams. [targetobject]: /{{page.kong_version}}/admin-api#target-object [addupstream]: /{{page.kong_version}}/admin-api#add-upstream [clustering]: /{{page.kong_version}}/clustering -[upstreamobjects]: /{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/gateway-oss/1.1.x/health-checks-circuit-breakers.md b/app/gateway-oss/1.1.x/health-checks-circuit-breakers.md index 4c588b96de87..83ea4c66586f 100644 --- a/app/gateway-oss/1.1.x/health-checks-circuit-breakers.md +++ b/app/gateway-oss/1.1.x/health-checks-circuit-breakers.md @@ -204,7 +204,7 @@ active health checks on `healthy` status to zero, and active checks on ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -318,6 +318,6 @@ upstreams. [targetobject]: /{{page.kong_version}}/admin-api#target-object [addupstream]: /{{page.kong_version}}/admin-api#add-upstream [clustering]: /{{page.kong_version}}/clustering -[upstreamobjects]: /{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/gateway-oss/1.2.x/health-checks-circuit-breakers.md b/app/gateway-oss/1.2.x/health-checks-circuit-breakers.md index 4c588b96de87..83ea4c66586f 100644 --- a/app/gateway-oss/1.2.x/health-checks-circuit-breakers.md +++ b/app/gateway-oss/1.2.x/health-checks-circuit-breakers.md @@ -204,7 +204,7 @@ active health checks on `healthy` status to zero, and active checks on ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -318,6 +318,6 @@ upstreams. [targetobject]: /{{page.kong_version}}/admin-api#target-object [addupstream]: /{{page.kong_version}}/admin-api#add-upstream [clustering]: /{{page.kong_version}}/clustering -[upstreamobjects]: /{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/gateway-oss/1.3.x/health-checks-circuit-breakers.md b/app/gateway-oss/1.3.x/health-checks-circuit-breakers.md index 4c588b96de87..83ea4c66586f 100644 --- a/app/gateway-oss/1.3.x/health-checks-circuit-breakers.md +++ b/app/gateway-oss/1.3.x/health-checks-circuit-breakers.md @@ -204,7 +204,7 @@ active health checks on `healthy` status to zero, and active checks on ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -318,6 +318,6 @@ upstreams. [targetobject]: /{{page.kong_version}}/admin-api#target-object [addupstream]: /{{page.kong_version}}/admin-api#add-upstream [clustering]: /{{page.kong_version}}/clustering -[upstreamobjects]: /{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/gateway-oss/1.4.x/health-checks-circuit-breakers.md b/app/gateway-oss/1.4.x/health-checks-circuit-breakers.md index 4c588b96de87..83ea4c66586f 100644 --- a/app/gateway-oss/1.4.x/health-checks-circuit-breakers.md +++ b/app/gateway-oss/1.4.x/health-checks-circuit-breakers.md @@ -204,7 +204,7 @@ active health checks on `healthy` status to zero, and active checks on ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -318,6 +318,6 @@ upstreams. [targetobject]: /{{page.kong_version}}/admin-api#target-object [addupstream]: /{{page.kong_version}}/admin-api#add-upstream [clustering]: /{{page.kong_version}}/clustering -[upstreamobjects]: /{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/gateway-oss/1.5.x/health-checks-circuit-breakers.md b/app/gateway-oss/1.5.x/health-checks-circuit-breakers.md index 4c588b96de87..83ea4c66586f 100644 --- a/app/gateway-oss/1.5.x/health-checks-circuit-breakers.md +++ b/app/gateway-oss/1.5.x/health-checks-circuit-breakers.md @@ -204,7 +204,7 @@ active health checks on `healthy` status to zero, and active checks on ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -318,6 +318,6 @@ upstreams. [targetobject]: /{{page.kong_version}}/admin-api#target-object [addupstream]: /{{page.kong_version}}/admin-api#add-upstream [clustering]: /{{page.kong_version}}/clustering -[upstreamobjects]: /{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/gateway-oss/2.0.x/health-checks-circuit-breakers.md b/app/gateway-oss/2.0.x/health-checks-circuit-breakers.md index a1acadc4336d..5027e86730e9 100644 --- a/app/gateway-oss/2.0.x/health-checks-circuit-breakers.md +++ b/app/gateway-oss/2.0.x/health-checks-circuit-breakers.md @@ -249,7 +249,7 @@ active health checks on `healthy` status to zero, and active checks on ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -363,6 +363,6 @@ upstreams. [targetobject]: /{{page.kong_version}}/admin-api#target-object [addupstream]: /{{page.kong_version}}/admin-api#add-upstream [clustering]: /{{page.kong_version}}/clustering -[upstreamobjects]: /{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/gateway-oss/2.1.x/health-checks-circuit-breakers.md b/app/gateway-oss/2.1.x/health-checks-circuit-breakers.md index a1085a074235..e82fb1dd4923 100644 --- a/app/gateway-oss/2.1.x/health-checks-circuit-breakers.md +++ b/app/gateway-oss/2.1.x/health-checks-circuit-breakers.md @@ -241,7 +241,7 @@ in order to re-enable it automatically. ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -355,6 +355,6 @@ upstreams. [targetobject]: /{{page.kong_version}}/admin-api#target-object [addupstream]: /{{page.kong_version}}/admin-api#add-upstream [clustering]: /{{page.kong_version}}/clustering -[upstreamobjects]: /{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/gateway-oss/2.2.x/health-checks-circuit-breakers.md b/app/gateway-oss/2.2.x/health-checks-circuit-breakers.md index a1085a074235..e82fb1dd4923 100644 --- a/app/gateway-oss/2.2.x/health-checks-circuit-breakers.md +++ b/app/gateway-oss/2.2.x/health-checks-circuit-breakers.md @@ -241,7 +241,7 @@ in order to re-enable it automatically. ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -355,6 +355,6 @@ upstreams. [targetobject]: /{{page.kong_version}}/admin-api#target-object [addupstream]: /{{page.kong_version}}/admin-api#add-upstream [clustering]: /{{page.kong_version}}/clustering -[upstreamobjects]: /{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/gateway-oss/2.3.x/health-checks-circuit-breakers.md b/app/gateway-oss/2.3.x/health-checks-circuit-breakers.md index a1085a074235..e82fb1dd4923 100644 --- a/app/gateway-oss/2.3.x/health-checks-circuit-breakers.md +++ b/app/gateway-oss/2.3.x/health-checks-circuit-breakers.md @@ -241,7 +241,7 @@ in order to re-enable it automatically. ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -355,6 +355,6 @@ upstreams. [targetobject]: /{{page.kong_version}}/admin-api#target-object [addupstream]: /{{page.kong_version}}/admin-api#add-upstream [clustering]: /{{page.kong_version}}/clustering -[upstreamobjects]: /{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/gateway-oss/2.4.x/health-checks-circuit-breakers.md b/app/gateway-oss/2.4.x/health-checks-circuit-breakers.md index 1b0eebf89cfa..342d2b34b18c 100644 --- a/app/gateway-oss/2.4.x/health-checks-circuit-breakers.md +++ b/app/gateway-oss/2.4.x/health-checks-circuit-breakers.md @@ -241,7 +241,7 @@ in order to re-enable it automatically. ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -355,6 +355,6 @@ upstreams. [targetobject]: /gateway-oss/{{page.kong_version}}/admin-api#target-object [addupstream]: /gateway-oss/{{page.kong_version}}/admin-api#add-upstream [clustering]: /gateway-oss/{{page.kong_version}}/clustering -[upstreamobjects]: /gateway-oss/{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /gateway-oss/{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /gateway-oss/{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /gateway-oss/{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/gateway-oss/2.5.x/health-checks-circuit-breakers.md b/app/gateway-oss/2.5.x/health-checks-circuit-breakers.md index 1b0eebf89cfa..342d2b34b18c 100644 --- a/app/gateway-oss/2.5.x/health-checks-circuit-breakers.md +++ b/app/gateway-oss/2.5.x/health-checks-circuit-breakers.md @@ -241,7 +241,7 @@ in order to re-enable it automatically. ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -355,6 +355,6 @@ upstreams. [targetobject]: /gateway-oss/{{page.kong_version}}/admin-api#target-object [addupstream]: /gateway-oss/{{page.kong_version}}/admin-api#add-upstream [clustering]: /gateway-oss/{{page.kong_version}}/clustering -[upstreamobjects]: /gateway-oss/{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /gateway-oss/{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /gateway-oss/{{page.kong_version}}/loadbalancing#balancing-caveats [dnscaveats]: /gateway-oss/{{page.kong_version}}/loadbalancing#dns-caveats diff --git a/app/gateway/2.6.x/reference/health-checks-circuit-breakers.md b/app/gateway/2.6.x/reference/health-checks-circuit-breakers.md index a244e855a354..4fb20e3dcfa8 100644 --- a/app/gateway/2.6.x/reference/health-checks-circuit-breakers.md +++ b/app/gateway/2.6.x/reference/health-checks-circuit-breakers.md @@ -235,7 +235,7 @@ in order to re-enable it automatically. ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -347,6 +347,6 @@ upstreams. [targetobject]: /gateway/{{page.kong_version}}/admin-api#target-object [addupstream]: /gateway/{{page.kong_version}}/admin-api#add-upstream [clustering]: /gateway/{{page.kong_version}}/reference/clustering -[upstreamobjects]: /gateway/{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /gateway/{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /gateway/{{page.kong_version}}/reference/loadbalancing#balancing-caveats [dnscaveats]: /gateway/{{page.kong_version}}/reference/loadbalancing#dns-caveats diff --git a/app/gateway/2.7.x/reference/health-checks-circuit-breakers.md b/app/gateway/2.7.x/reference/health-checks-circuit-breakers.md index a244e855a354..4fb20e3dcfa8 100644 --- a/app/gateway/2.7.x/reference/health-checks-circuit-breakers.md +++ b/app/gateway/2.7.x/reference/health-checks-circuit-breakers.md @@ -235,7 +235,7 @@ in order to re-enable it automatically. ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -347,6 +347,6 @@ upstreams. [targetobject]: /gateway/{{page.kong_version}}/admin-api#target-object [addupstream]: /gateway/{{page.kong_version}}/admin-api#add-upstream [clustering]: /gateway/{{page.kong_version}}/reference/clustering -[upstreamobjects]: /gateway/{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /gateway/{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /gateway/{{page.kong_version}}/reference/loadbalancing#balancing-caveats [dnscaveats]: /gateway/{{page.kong_version}}/reference/loadbalancing#dns-caveats diff --git a/app/gateway/2.8.x/reference/health-checks-circuit-breakers.md b/app/gateway/2.8.x/reference/health-checks-circuit-breakers.md index a244e855a354..4fb20e3dcfa8 100644 --- a/app/gateway/2.8.x/reference/health-checks-circuit-breakers.md +++ b/app/gateway/2.8.x/reference/health-checks-circuit-breakers.md @@ -235,7 +235,7 @@ in order to re-enable it automatically. ### Enabling active health checks To enable active health checks, you need to specify the configuration items -under `healthchecks.active` in the [Upstream object][upstreamobjects] configuration. You +under `healthchecks.active` in the [Upstream object][upstreamobject] configuration. You need to specify the necessary information so that Kong can perform periodic probing on the target, and how to interpret the resulting information. @@ -347,6 +347,6 @@ upstreams. [targetobject]: /gateway/{{page.kong_version}}/admin-api#target-object [addupstream]: /gateway/{{page.kong_version}}/admin-api#add-upstream [clustering]: /gateway/{{page.kong_version}}/reference/clustering -[upstreamobjects]: /gateway/{{page.kong_version}}/admin-api#upstream-objects +[upstreamobject]: /gateway/{{page.kong_version}}/admin-api#upstream-object [balancercaveats]: /gateway/{{page.kong_version}}/reference/loadbalancing#balancing-caveats [dnscaveats]: /gateway/{{page.kong_version}}/reference/loadbalancing#dns-caveats diff --git a/app/kubernetes-ingress-controller/1.0.x/concepts/custom-resources.md b/app/kubernetes-ingress-controller/1.0.x/concepts/custom-resources.md index 13a373001992..ad29806e45a4 100644 --- a/app/kubernetes-ingress-controller/1.0.x/concepts/custom-resources.md +++ b/app/kubernetes-ingress-controller/1.0.x/concepts/custom-resources.md @@ -128,4 +128,4 @@ Instead, please use secret-based credentials. [kong-plugin]: /gateway/latest/admin-api/#plugin-object [kong-route]: /gateway/latest/admin-api/#route-object [kong-service]: /gateway/latest/admin-api/#service-object -[kong-upstream]: /gateway/latest/admin-api/#upstream-objects +[kong-upstream]: /gateway/latest/admin-api/#upstream-object diff --git a/app/kubernetes-ingress-controller/1.0.x/references/custom-resources.md b/app/kubernetes-ingress-controller/1.0.x/references/custom-resources.md index 73b0dc926c9a..68f28bb83ba6 100644 --- a/app/kubernetes-ingress-controller/1.0.x/references/custom-resources.md +++ b/app/kubernetes-ingress-controller/1.0.x/references/custom-resources.md @@ -399,7 +399,7 @@ resource: - `key-auth` for [Key authentication](https://docs.konghq.com/plugins/key-authentication/) - `basic-auth` for [Basic authenticaiton](https://docs.konghq.com/plugins/basic-authentication/) -- `hmac-auth` for [HMAC authentication](http://docs.konghq.com/plugins/hmac-authentication/) +- `hmac-auth` for [HMAC authentication](http://docs.konghq.com/plugins/hmac-auth/) - `jwt` for [JWT based authentication](http://docs.konghq.com/plugins/jwt/) - `oauth2` for [Oauth2 Client credentials](https://docs.konghq.com/hub/kong-inc/oauth2/) - `acl` for [ACL group associations](https://docs.konghq.com/hub/kong-inc/acl/) @@ -414,6 +414,6 @@ guide for details on how to use this resource. [k8s-crd]: https://kubernetes.io/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/ [kong-consumer]: /gateway/latest/admin-api/#consumer-object [kong-plugin]: /gateway/latest/admin-api/#plugin-object -[kong-upstream]: /gateway/latest/admin-api/#upstream-objects +[kong-upstream]: /gateway/latest/admin-api/#upstream-object [kong-service]: /gateway/latest/admin-api/#service-object [kong-route]: /gateway/latest/admin-api/#route-object diff --git a/app/kubernetes-ingress-controller/1.1.x/concepts/custom-resources.md b/app/kubernetes-ingress-controller/1.1.x/concepts/custom-resources.md index 13a373001992..ad29806e45a4 100644 --- a/app/kubernetes-ingress-controller/1.1.x/concepts/custom-resources.md +++ b/app/kubernetes-ingress-controller/1.1.x/concepts/custom-resources.md @@ -128,4 +128,4 @@ Instead, please use secret-based credentials. [kong-plugin]: /gateway/latest/admin-api/#plugin-object [kong-route]: /gateway/latest/admin-api/#route-object [kong-service]: /gateway/latest/admin-api/#service-object -[kong-upstream]: /gateway/latest/admin-api/#upstream-objects +[kong-upstream]: /gateway/latest/admin-api/#upstream-object diff --git a/app/kubernetes-ingress-controller/1.1.x/references/custom-resources.md b/app/kubernetes-ingress-controller/1.1.x/references/custom-resources.md index 73b0dc926c9a..68f28bb83ba6 100644 --- a/app/kubernetes-ingress-controller/1.1.x/references/custom-resources.md +++ b/app/kubernetes-ingress-controller/1.1.x/references/custom-resources.md @@ -399,7 +399,7 @@ resource: - `key-auth` for [Key authentication](https://docs.konghq.com/plugins/key-authentication/) - `basic-auth` for [Basic authenticaiton](https://docs.konghq.com/plugins/basic-authentication/) -- `hmac-auth` for [HMAC authentication](http://docs.konghq.com/plugins/hmac-authentication/) +- `hmac-auth` for [HMAC authentication](http://docs.konghq.com/plugins/hmac-auth/) - `jwt` for [JWT based authentication](http://docs.konghq.com/plugins/jwt/) - `oauth2` for [Oauth2 Client credentials](https://docs.konghq.com/hub/kong-inc/oauth2/) - `acl` for [ACL group associations](https://docs.konghq.com/hub/kong-inc/acl/) @@ -414,6 +414,6 @@ guide for details on how to use this resource. [k8s-crd]: https://kubernetes.io/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/ [kong-consumer]: /gateway/latest/admin-api/#consumer-object [kong-plugin]: /gateway/latest/admin-api/#plugin-object -[kong-upstream]: /gateway/latest/admin-api/#upstream-objects +[kong-upstream]: /gateway/latest/admin-api/#upstream-object [kong-service]: /gateway/latest/admin-api/#service-object [kong-route]: /gateway/latest/admin-api/#route-object diff --git a/app/kubernetes-ingress-controller/1.2.x/concepts/custom-resources.md b/app/kubernetes-ingress-controller/1.2.x/concepts/custom-resources.md index 13a373001992..ad29806e45a4 100644 --- a/app/kubernetes-ingress-controller/1.2.x/concepts/custom-resources.md +++ b/app/kubernetes-ingress-controller/1.2.x/concepts/custom-resources.md @@ -128,4 +128,4 @@ Instead, please use secret-based credentials. [kong-plugin]: /gateway/latest/admin-api/#plugin-object [kong-route]: /gateway/latest/admin-api/#route-object [kong-service]: /gateway/latest/admin-api/#service-object -[kong-upstream]: /gateway/latest/admin-api/#upstream-objects +[kong-upstream]: /gateway/latest/admin-api/#upstream-object diff --git a/app/kubernetes-ingress-controller/1.2.x/references/custom-resources.md b/app/kubernetes-ingress-controller/1.2.x/references/custom-resources.md index 73b0dc926c9a..68f28bb83ba6 100644 --- a/app/kubernetes-ingress-controller/1.2.x/references/custom-resources.md +++ b/app/kubernetes-ingress-controller/1.2.x/references/custom-resources.md @@ -399,7 +399,7 @@ resource: - `key-auth` for [Key authentication](https://docs.konghq.com/plugins/key-authentication/) - `basic-auth` for [Basic authenticaiton](https://docs.konghq.com/plugins/basic-authentication/) -- `hmac-auth` for [HMAC authentication](http://docs.konghq.com/plugins/hmac-authentication/) +- `hmac-auth` for [HMAC authentication](http://docs.konghq.com/plugins/hmac-auth/) - `jwt` for [JWT based authentication](http://docs.konghq.com/plugins/jwt/) - `oauth2` for [Oauth2 Client credentials](https://docs.konghq.com/hub/kong-inc/oauth2/) - `acl` for [ACL group associations](https://docs.konghq.com/hub/kong-inc/acl/) @@ -414,6 +414,6 @@ guide for details on how to use this resource. [k8s-crd]: https://kubernetes.io/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/ [kong-consumer]: /gateway/latest/admin-api/#consumer-object [kong-plugin]: /gateway/latest/admin-api/#plugin-object -[kong-upstream]: /gateway/latest/admin-api/#upstream-objects +[kong-upstream]: /gateway/latest/admin-api/#upstream-object [kong-service]: /gateway/latest/admin-api/#service-object [kong-route]: /gateway/latest/admin-api/#route-object diff --git a/app/kubernetes-ingress-controller/1.3.x/concepts/custom-resources.md b/app/kubernetes-ingress-controller/1.3.x/concepts/custom-resources.md index 13a373001992..ad29806e45a4 100644 --- a/app/kubernetes-ingress-controller/1.3.x/concepts/custom-resources.md +++ b/app/kubernetes-ingress-controller/1.3.x/concepts/custom-resources.md @@ -128,4 +128,4 @@ Instead, please use secret-based credentials. [kong-plugin]: /gateway/latest/admin-api/#plugin-object [kong-route]: /gateway/latest/admin-api/#route-object [kong-service]: /gateway/latest/admin-api/#service-object -[kong-upstream]: /gateway/latest/admin-api/#upstream-objects +[kong-upstream]: /gateway/latest/admin-api/#upstream-object diff --git a/app/kubernetes-ingress-controller/1.3.x/references/custom-resources.md b/app/kubernetes-ingress-controller/1.3.x/references/custom-resources.md index 73b0dc926c9a..68f28bb83ba6 100644 --- a/app/kubernetes-ingress-controller/1.3.x/references/custom-resources.md +++ b/app/kubernetes-ingress-controller/1.3.x/references/custom-resources.md @@ -399,7 +399,7 @@ resource: - `key-auth` for [Key authentication](https://docs.konghq.com/plugins/key-authentication/) - `basic-auth` for [Basic authenticaiton](https://docs.konghq.com/plugins/basic-authentication/) -- `hmac-auth` for [HMAC authentication](http://docs.konghq.com/plugins/hmac-authentication/) +- `hmac-auth` for [HMAC authentication](http://docs.konghq.com/plugins/hmac-auth/) - `jwt` for [JWT based authentication](http://docs.konghq.com/plugins/jwt/) - `oauth2` for [Oauth2 Client credentials](https://docs.konghq.com/hub/kong-inc/oauth2/) - `acl` for [ACL group associations](https://docs.konghq.com/hub/kong-inc/acl/) @@ -414,6 +414,6 @@ guide for details on how to use this resource. [k8s-crd]: https://kubernetes.io/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/ [kong-consumer]: /gateway/latest/admin-api/#consumer-object [kong-plugin]: /gateway/latest/admin-api/#plugin-object -[kong-upstream]: /gateway/latest/admin-api/#upstream-objects +[kong-upstream]: /gateway/latest/admin-api/#upstream-object [kong-service]: /gateway/latest/admin-api/#service-object [kong-route]: /gateway/latest/admin-api/#route-object diff --git a/app/kubernetes-ingress-controller/2.0.x/concepts/custom-resources.md b/app/kubernetes-ingress-controller/2.0.x/concepts/custom-resources.md index 896d2bd5ac75..39f02e7357f7 100644 --- a/app/kubernetes-ingress-controller/2.0.x/concepts/custom-resources.md +++ b/app/kubernetes-ingress-controller/2.0.x/concepts/custom-resources.md @@ -131,4 +131,4 @@ VPN software and a variety of other applications. [kong-plugin]: /gateway/latest/admin-api/#plugin-object [kong-route]: /gateway/latest/admin-api/#route-object [kong-service]: /gateway/latest/admin-api/#service-object -[kong-upstream]: /gateway/latest/admin-api/#upstream-objects +[kong-upstream]: /gateway/latest/admin-api/#upstream-object diff --git a/app/kubernetes-ingress-controller/2.0.x/references/custom-resources.md b/app/kubernetes-ingress-controller/2.0.x/references/custom-resources.md index ce346dd62692..85be16614aca 100644 --- a/app/kubernetes-ingress-controller/2.0.x/references/custom-resources.md +++ b/app/kubernetes-ingress-controller/2.0.x/references/custom-resources.md @@ -414,6 +414,6 @@ For help configuring credentials for the `KongConsumer` Please refer to the [usi [k8s-crd]: https://kubernetes.io/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/ [kong-consumer]: /gateway/latest/admin-api/#consumer-object [kong-plugin]: /gateway/latest/admin-api/#plugin-object -[kong-upstream]: /gateway/latest/admin-api/#upstream-objects +[kong-upstream]: /gateway/latest/admin-api/#upstream-object [kong-service]: /gateway/latest/admin-api/#service-object [kong-route]: /gateway/latest/admin-api/#route-object diff --git a/app/kubernetes-ingress-controller/2.1.x/concepts/custom-resources.md b/app/kubernetes-ingress-controller/2.1.x/concepts/custom-resources.md index 896d2bd5ac75..39f02e7357f7 100644 --- a/app/kubernetes-ingress-controller/2.1.x/concepts/custom-resources.md +++ b/app/kubernetes-ingress-controller/2.1.x/concepts/custom-resources.md @@ -131,4 +131,4 @@ VPN software and a variety of other applications. [kong-plugin]: /gateway/latest/admin-api/#plugin-object [kong-route]: /gateway/latest/admin-api/#route-object [kong-service]: /gateway/latest/admin-api/#service-object -[kong-upstream]: /gateway/latest/admin-api/#upstream-objects +[kong-upstream]: /gateway/latest/admin-api/#upstream-object diff --git a/app/kubernetes-ingress-controller/2.1.x/references/custom-resources.md b/app/kubernetes-ingress-controller/2.1.x/references/custom-resources.md index e28757394494..2f2ec4d5ee80 100644 --- a/app/kubernetes-ingress-controller/2.1.x/references/custom-resources.md +++ b/app/kubernetes-ingress-controller/2.1.x/references/custom-resources.md @@ -414,6 +414,6 @@ For help configuring credentials for the `KongConsumer` Please refer to the [usi [k8s-crd]: https://kubernetes.io/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/ [kong-consumer]: /gateway/latest/admin-api/#consumer-object [kong-plugin]: /gateway/latest/admin-api/#plugin-object -[kong-upstream]: /gateway/latest/admin-api/#upstream-objects +[kong-upstream]: /gateway/latest/admin-api/#upstream-object [kong-service]: /gateway/latest/admin-api/#service-object [kong-route]: /gateway/latest/admin-api/#route-object diff --git a/app/kubernetes-ingress-controller/2.2.x/concepts/custom-resources.md b/app/kubernetes-ingress-controller/2.2.x/concepts/custom-resources.md index 896d2bd5ac75..39f02e7357f7 100644 --- a/app/kubernetes-ingress-controller/2.2.x/concepts/custom-resources.md +++ b/app/kubernetes-ingress-controller/2.2.x/concepts/custom-resources.md @@ -131,4 +131,4 @@ VPN software and a variety of other applications. [kong-plugin]: /gateway/latest/admin-api/#plugin-object [kong-route]: /gateway/latest/admin-api/#route-object [kong-service]: /gateway/latest/admin-api/#service-object -[kong-upstream]: /gateway/latest/admin-api/#upstream-objects +[kong-upstream]: /gateway/latest/admin-api/#upstream-object diff --git a/app/kubernetes-ingress-controller/2.2.x/references/custom-resources.md b/app/kubernetes-ingress-controller/2.2.x/references/custom-resources.md index e28757394494..2f2ec4d5ee80 100644 --- a/app/kubernetes-ingress-controller/2.2.x/references/custom-resources.md +++ b/app/kubernetes-ingress-controller/2.2.x/references/custom-resources.md @@ -414,6 +414,6 @@ For help configuring credentials for the `KongConsumer` Please refer to the [usi [k8s-crd]: https://kubernetes.io/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/ [kong-consumer]: /gateway/latest/admin-api/#consumer-object [kong-plugin]: /gateway/latest/admin-api/#plugin-object -[kong-upstream]: /gateway/latest/admin-api/#upstream-objects +[kong-upstream]: /gateway/latest/admin-api/#upstream-object [kong-service]: /gateway/latest/admin-api/#service-object [kong-route]: /gateway/latest/admin-api/#route-object diff --git a/app/kubernetes-ingress-controller/2.3.x/concepts/custom-resources.md b/app/kubernetes-ingress-controller/2.3.x/concepts/custom-resources.md index 896d2bd5ac75..39f02e7357f7 100644 --- a/app/kubernetes-ingress-controller/2.3.x/concepts/custom-resources.md +++ b/app/kubernetes-ingress-controller/2.3.x/concepts/custom-resources.md @@ -131,4 +131,4 @@ VPN software and a variety of other applications. [kong-plugin]: /gateway/latest/admin-api/#plugin-object [kong-route]: /gateway/latest/admin-api/#route-object [kong-service]: /gateway/latest/admin-api/#service-object -[kong-upstream]: /gateway/latest/admin-api/#upstream-objects +[kong-upstream]: /gateway/latest/admin-api/#upstream-object diff --git a/app/kubernetes-ingress-controller/2.3.x/references/custom-resources.md b/app/kubernetes-ingress-controller/2.3.x/references/custom-resources.md index e28757394494..2f2ec4d5ee80 100644 --- a/app/kubernetes-ingress-controller/2.3.x/references/custom-resources.md +++ b/app/kubernetes-ingress-controller/2.3.x/references/custom-resources.md @@ -414,6 +414,6 @@ For help configuring credentials for the `KongConsumer` Please refer to the [usi [k8s-crd]: https://kubernetes.io/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/ [kong-consumer]: /gateway/latest/admin-api/#consumer-object [kong-plugin]: /gateway/latest/admin-api/#plugin-object -[kong-upstream]: /gateway/latest/admin-api/#upstream-objects +[kong-upstream]: /gateway/latest/admin-api/#upstream-object [kong-service]: /gateway/latest/admin-api/#service-object [kong-route]: /gateway/latest/admin-api/#route-object