Skip to main content
Closed beta. Publishing a service is part of Managed services, which is in closed beta and enabled per organisation on request. Contact support to have it turned on for your organisation.
Publishing turns one version of a stack profile your organisation owns into a package in your organisation’s service catalogue. You say what kind of service the profile runs, which Kubernetes Service applications connect to, and which Secret holds its login. From then on, anyone who can deploy applications sets it up from the catalogue like one of Ankra’s own services: Ankra installs the pinned profile version into a namespace named after each service, hands each connected application the address and login as environment variables, and checks the service’s health. At the end you have a package marked Published by this organisation in the catalogue, ready to set up.

Before you start

  • Managed services are turned on for your organisation. Infrastructure → Managed services opens. If it says Managed services are not available to your organisation yet., choose Contact support.
  • A stack profile your organisation owns, with a version that is not withdrawn. A profile shared with your organisation, or a public one, cannot be published by you. See Stack Profiles to build one.
  • The profile runs an engine Ankra can connect applications to. The kinds of service are PostgreSQL, Redis, NATS, OpenSearch, S3-compatible object storage, VictoriaLogs and VictoriaMetrics. Something people use directly, such as a web tool, belongs in a stack profile, not a service.
  • Your role holds profiles.write. Without it the page says Your role cannot publish services. Trying a connection on a running demo also needs stacks.deploy.
  • Optional: a running demo of the profile. With one, Ankra fills in the connection for you and tries it before you publish. The portal has no page that launches a demo: launch it with ankra stack-profiles demo launch, as under Stack Profile Demos.

Publish the profile

1

Open the publish page

Go to Build & delivery → Stack profiles and choose Make this a service on a profile your organisation owns. From the catalogue, Infrastructure → Managed services → Catalogue has a Publish your own service section whose Choose a stack profile button opens the same list.The page Publish your profile as a service opens with What this profile installs: the add-ons in the profile’s latest version and their namespaces.
2

Check what Ankra suggests

Under the add-ons, a card labelled AI suggestion says what the profile runs (This runs <engine>), and that kind is chosen for you below. Ankra also matches the chart names, so a well-known chart is suggested even without the card. If the card says This is an application people use, not a service, install the profile from Stack profiles instead of publishing it.
3

Fill it from a running demo (optional)

Under Fill it from a running demo, the page looks for a running demo of the profile. When it finds one, choose Fill from the running demo: Ankra reads the demo’s Services and Secrets, never the Secret values, and fills in the connection. The page says The connection below was filled from the demo. and names any value it could not find.Ankra also checks whether two services from the package could share one cluster. Two services from this package can share a cluster. is the answer you want. When it says they would collide, it lists the cluster-wide objects, such as a ClusterRole or a CRD, that both would claim.Without a running demo, the section says No demo of this profile is running. Fill in the next steps by hand.
4

Choose the kind of service

Under What kind of service is it?, choose the Kind of service. It decides which connection details applications receive, and sets the Port and the Category to their usual values.
5

Say where applications find it

Under Where applications find it, enter the Kubernetes Service applications connect to and its Port, and the Kubernetes Secret, in the same namespace, that holds the login. Each connected application’s deployment reads that Secret inside the cluster, so the password is never copied into the catalogue or sent to Ankra. Where do I find these? explains where the chart usually creates them.What a connected application receives lists each environment variable and where its value comes from. The usual places are filled in. To change one, open Change where a value comes from and choose A key of the Secret, A fixed value, The Service’s host name, or The Service’s host name and port. A password or other credential cannot be a fixed value.
6

Try it on the demo (optional)

With a running demo, choose Try it on the demo. Ankra runs the same readiness check that checks a published service, inside the demo’s namespace. The connection works on the demo. means applications will be able to connect the way you described.
7

Name the package and publish

Under How it appears in the catalogue, check the Name in the catalogue (lowercase letters, digits and single hyphens, starting with a letter, at most 63 characters), the Version (three numbers, such as 1.0.0), the Profile version it installs, and the Category. Setting up the service installs exactly that profile version.Choose Publish to the service catalogue. The package’s page opens.
A published version never changes. To change anything, publish a new Version number. Publishing the same name and version again with different settings is refused.

Verify

  1. Open Infrastructure → Managed services → Catalogue. The package is listed, marked Published by this organisation. From the command line, ankra services packages list lists it.
  2. Open it and choose Set up, then follow Set Up a Managed Service. Once the service runs, its page shows its Service health and Readiness, as for Ankra’s own services: see Health and readiness.
A package published from the portal runs on Your infrastructure and has no settings to choose at setup. Each service set up from it runs in its own namespace, named after the service, whatever namespace the profile names on its own.

What can go wrong


Next steps

Set up a managed service

Set the published package up for an application.

Stack profile demos

Run the profile on your staging cluster before you publish it.

Connect to a managed service

The variables a connected application reads, for each kind of service.

Stack profiles

Build and version the profile a package installs.