Configuring a Service

Using the Service Hub, you can create, manage, and implement Konnect services. Each service consists of at least one service version, and each service version can have one implementation.

For the purpose of this guide, you’ll create a service, version it, and expose the version by creating an implementation pointing to the Mockbin API. Mockbin is an echo-type public website that returns requests back to the requester as responses.

Prerequisites

If you’re following the Konnect quickstart guide, make sure you have configured a runtime.

Create a service

1. From the left navigation menu, open Service Hub.

2. Click New service.

3. Enter a display name. For this example, enter example_service.

   A display name can be any string containing letters, numbers, spaces, or the following characters: ., -, _, ~, or :. Spaces are equal to the - character.

   For example, you can use example_service, ExampleService, Example-Service, or Example Service. Example-Service and Example Service would be considered the same name.

   The display name you create generates a service name. Konnect uses the service name for internal metadata.

4. (Optional) Enter a description.

   This description is used in Konnect and on the Dev Portal.

5. Click Create.

   You can now see your new service’s overview page.

   Now that you have a service set up, you can start filling out details about your API.

Create a service version

Let’s set up the first version of your API service.

1. In the Service Hub, open the example_service service and click Service actions > Add new version.

2. Enter a version name. For this example, enter v1.

   A version name can be any string containing letters, numbers, or characters; for example, 1.0.0, v1, or version#1. A service can have multiple versions.

3. Select a runtime group.

   Choose a group to deploy this service version to. This lets you deploy to a specific group of runtime instances in a specific environment.

   Note: Application registration is only available for services in the default runtime group, so if you plan on using application registration, choose default in this step.

   Different versions of the same service can run in different runtime groups. The version name is unique within a group:

   • If you create multiple versions in the same group, they must have unique names.
   • If you create multiple versions in different groups, the versions can have the same name.

4. Click Save.

Summary and next steps

In this section, you added a service named example_service with the version v1.

Next, go on to implement the service version.