-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QA (landing pages & reference) #187
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -29,7 +29,7 @@ schema: | |||||
|
||||||
## What is a route? | ||||||
|
||||||
{{page.description}} Services can store collections of objects like plugin configurations, and policies, and they can be associated with routes. In {{site.base_gateway}}, routes typically map to endpoints that are exposed through the {{site.base_gateway}} application. Routes can also define rules that match requests to associated services. Because of this, one route can reference multiple endpoints. A basic route should have a name, path or paths, and reference an existing service. | ||||||
{{page.description | liquify}} Services can store collections of objects like plugin configurations, and policies, and they can be associated with routes. In {{site.base_gateway}}, routes typically map to endpoints that are exposed through the {{site.base_gateway}} application. Routes can also define rules that match requests to associated services. Because of this, one route can reference multiple endpoints. A basic route should have a name, path or paths, and reference an existing service. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
You can also configure routes with: | ||||||
|
||||||
|
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -34,7 +34,7 @@ api_specs: | |||||
|
||||||
## What is a Gateway Service? | ||||||
|
||||||
{{ page.description }} | ||||||
{{ page.description | liquify }} | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
Services can store collections of objects like plugin configurations, and policies, and they can be associated with routes. | ||||||
|
||||||
When defining a Service, the administrator provides a name and the upstream application connection information. | ||||||
|
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -27,7 +27,7 @@ schema: | |||||
|
||||||
## What is a Target? | ||||||
|
||||||
{{page.description}} Each [Upstream](/gateway/entities/upstream/) can have many Targets. Targets are used by Upstreams for [load balancing](https://docs.konghq.com/gateway/latest/how-kong-works/load-balancing/). For example, if you have an `example_upstream` Upstream, you can point it to two different Targets: `httpbin.konghq.com` and `httpbun.com`. This is so that if one of the servers (like `httpbin.konghq.com`) is unavailable, it automatically detects the problem and routes all traffic to the working server (`httpbun.com`). | ||||||
{{page.description | liquify}} Each [Upstream](/gateway/entities/upstream/) can have many Targets. Targets are used by Upstreams for [load balancing](https://docs.konghq.com/gateway/latest/how-kong-works/load-balancing/). For example, if you have an `example_upstream` Upstream, you can point it to two different Targets: `httpbin.konghq.com` and `httpbun.com`. This is so that if one of the servers (like `httpbin.konghq.com`) is unavailable, it automatically detects the problem and routes all traffic to the working server (`httpbun.com`). | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
The following diagram illustrates how Targets are used by Upstreams for load balancing: | ||||||
|
||||||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -18,6 +18,8 @@ schema: | |
path: /schemas/Workspace | ||
--- | ||
|
||
TODO | ||
|
||
## What is a workspace? | ||
|
||
This page is a stub | ||
|
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -20,7 +20,7 @@ breadcrumbs: | |||||
- /deck/ | ||||||
--- | ||||||
|
||||||
{{ page.description }} | ||||||
{{ page.description | liquify }} | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
You can do this by breaking up the configuration into multiple files and managing them using tags. | ||||||
|
||||||
With tags, you can use decK's `select-tag` feature to export, sync, or reset | ||||||
|
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -23,7 +23,7 @@ breadcrumbs: | |||||
- /deck/ | ||||||
--- | ||||||
|
||||||
{{ page.description }} | ||||||
{{ page.description | liquify }} | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
Adjust `KONG_ADMIN_HOST` and the port `8001` in the following examples to the | ||||||
host and port of your own {{site.base_gateway}} instance. | ||||||
|
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -24,7 +24,7 @@ breadcrumbs: | |||||
- /deck/ | ||||||
--- | ||||||
|
||||||
{{ page.description }} You can see what the defaults are for each object in the | ||||||
{{ page.description | liquify }} You can see what the defaults are for each object in the | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
[Admin API reference](https://docs.konghq.com/gateway/latest/admin-api/), or use the | ||||||
[`/schemas`](#find-defaults-for-an-object) endpoint to | ||||||
check the latest object schemas for your instance of the {{site.base_gateway}}. | ||||||
|
@@ -45,7 +45,7 @@ enforce a set of standard values and avoid repetition in your configuration. | |||||
decK assigns values in the following order of precedence, from highest to lowest: | ||||||
|
||||||
1. Values set for a specific instance of an object in the state file | ||||||
(for example, for a service named `example_service` defined in `kong.yml`). | ||||||
(for example, for a Gateway Service named `example_service` defined in `kong.yaml`). | ||||||
2. Values set in the `{_info: defaults:}` object in the state file. | ||||||
3. Self-managed {{site.base_gateway}} only: Values are checked against the Kong | ||||||
Admin API schemas. | ||||||
|
@@ -237,7 +237,7 @@ For all available properties, see the | |||||
Use the Kong Admin API `/schemas` endpoint to find default values: | ||||||
|
||||||
```sh | ||||||
curl -i http://localhost:8001/schemas/plugins/<plugin-name> | ||||||
curl -i http://localhost:8001/schemas/plugins/$PLUGIN_NAME | ||||||
``` | ||||||
|
||||||
decK doesn't support setting custom default values for the plugin object. | ||||||
|
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -22,7 +22,7 @@ breadcrumbs: | |||||
- /gateway/routing/ | ||||||
--- | ||||||
|
||||||
{{ page.description }} Expressions can be used to perform tasks such as defining | ||||||
{{ page.description | liquify }} Expressions can be used to perform tasks such as defining | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
complex routing logic. | ||||||
This guide is a reference for the expressions language and explains how it can be used. | ||||||
|
||||||
|
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -44,7 +44,7 @@ breadcrumbs: | |||||
|
||||||
## What are API specs? | ||||||
|
||||||
{{ page.description }} | ||||||
{{ page.description | liquify }} | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
API specs can function like API documentation, but they also explain the values, parameters, and objects in the schema of the API. An API spec helps users know how to make requests to the APIs contained within the spec. | ||||||
|
||||||
## How does Insomnia parse API specs? | ||||||
|
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -33,7 +33,7 @@ faqs: | |||||
|
||||||
--- | ||||||
|
||||||
{{page.description}} | ||||||
{{page.description | liquify}} | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
This feature is beneficial for collaboration, providing easy access to projects from different devices and locations. | ||||||
|
||||||
Cloud sync provides the following abilities on top of the base Insomnia functionality: | ||||||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fabian recommended just putting the description directly in the intro paragraph on one of my other PRs.