(Legacy) Implement and Test a Service
This documentation is for the legacy Konnect environment at
konnect.konghq.com. For the
cloud.konghq.com environment, see the
current Konnect documentation.
Create a Service implementation to expose your Service to clients.
When you create an implementation, you also specify the Route to it. This Route,
combined with the proxy URL for the Service, will lead to the endpoint
specified in the Service implementation.
If you’re following the Konnect quickstart guide,
make sure you have
configured a Service.
Implement a Service Version
On the example_service overview, in the Versions section, click v.1.
Click New Implementation.
In the Create Implementation dialog, in step 1, create a new Service
implementation to associate with your Service version.
Click the Add using URL radio button. This is the default.
In the URL field, enter
Use the defaults for the 6 Advanced Fields.
In step 2, Add a Route to add a route to your Service Implementation.
For this example, enter the following:
For Name, enter
For Method, enter
For Path(s), click Add Path and enter
For the remaining fields, use the default values listed.
The v.1 Service Version overview displays.
If you want to view the configuration, edit or delete the implementation,
or delete the version, click the Actions menu.
Verify the Implementation
If you used the Docker script to create a container
earlier in Configure a Runtime,
your runtime’s default proxy URL is
Enter the proxy URL into your browser’s address bar and append the route path
you just set. The final URL should look something like this:
If successful, you should see the homepage for
mockbin.org. On your Service
Version overview page, you’ll see a record for status code 200. This might
take a few moments.
And that’s it! You have your first service set up, running, and routing
traffic proxied through a Kong Gateway runtime.
Summary and Next Steps
To summarize, in this topic you:
- Implemented the Service version
v.1 with the Route
/mock. This means if an HTTP
request is sent to the Kong Gateway node and it matches route
request is sent to
- Abstracted a backend/upstream service and put a route of your choice on the
front end, which you can now give to clients to make requests.
For next steps, check out some of the other things you can do in