Cloudsmith - Repositories - Kong Inc. (kong) - kuma-legacy (kuma-legacy)

Package Search Help

You can use boolean logic (e.g. AND/OR/NOT) for complex search queries. For more help and examples, see the search documentation.

Search by package name:
my-package _(implicit)
name:my-package _(explicit)

Search by package filename:
filename:my-package.ext

Search by package tag:
tag:latest

Search by package version:
version:1.0.0 prerelease:true _{(prereleases)}
prerelease:false _{(no prereleases)}

Search by package architecture:
architecture:x86_64

Search by package distribution:
distribution:el

Search by package license:
license:MIT

Search by package format:
format:deb

Search by package status:
status:in_progress

Search by package file checksum:
checksum:5afba

Search by package security status:
severity:critical

Search by package vulnerabilities:
vulnerabilities:>1
vulnerabilities:<1000

Search by # of package downloads:
downloads:>8
downloads:<100

Search by package type:
type:binary
type:source

Search by package size (bytes):
size:>50000
size:<10000

Search by dependency name/version:
dependency:log4j
dependency:log4j=1.0.0
dependency:log4j>1.0.0

Search by uploaded date:
uploaded:>"1 day ago"
uploaded:<"August 14, 2022 EST"

Search by entitlement token (identifier):
entitlement:3lKPVJPosCsY

Search by policy violation:
policy_violated:true
deny_policy_violated:true
license_policy_violated:true
vulnerability_policy_violated:true

Search by repository:
repository:repo-name

Search by last download date:
last_downloaded:<"30 days ago"
last_downloaded:>"August 14, 2022 EST"

Search queries for all Debian-specific (and related) package types

Search by component:
deb_component:unstable

Search queries for all Maven-specific (and related) package types

Search by group ID:
maven_group_id:org.apache

Search queries for all Docker-specific (and related) package types

Search by image digest:
docker_image_digest:sha256:7c5..6d4
(full hashref only)

Search by layer digest:
docker_layer_digest:sha256:4c4..ae4
(full hashref only)

Search queries for all Generic-specific package types

Search by file path:
generic_filepath:path/to/file.txt

Search by directory:
generic_directory:path/to

Field type modifiers (depending on the type, you can influence behaviour)

For all queries, you can use:
~foo for negation

For string queries, you can use:
^foo to anchor to start of term
foo$ to anchor to end of term
foo*bar for fuzzy matching

For number/date or version queries, you can use:
>foo for values greater than
>=foo for values greater / equal
<foo for values less than
<=foo for values less / equal

Need a secure and centralised artifact repository to deliver AI Skills, Alpine, Cargo, CocoaPods, Composer, Conan, Conda, CRAN, Dart, Debian, Docker, Generic, Go, Helm, Hex, HuggingFace, LuaRocks, Maven, MCP, Nix, npm, NuGet, P2, Python, RedHat, Ruby, Swift, Terraform, Vagrant, VSX, Raw & More packages?

Cloudsmith is the new standard in Package / Artifact Management and Software Distribution.

With support for all major package formats, you can trust us to manage your software supply chain.

Start My Free Trial

Set Me Up

Public — kong (Kong Inc.) / kuma-legacy

The multi-zone service mesh for containers, Kubernetes and VMs.

Info
- Instructions For:
- Alpine

Tool-Specific Instructions

Although we use GPG (and RSA) keys across each repository and package format, client-side tools might have specific instructions that differ (or require manual steps). To add or use the signing key for these tools, please click on the package format specific tabs above.

Public GPG Key

GPG-based keys/signatures are used by:

The public GPG key for the kong/kuma-legacy is:

It has the following long (20 bytes) and short (8 bytes) fingerprints:

68E613D00E7272A760BD9DA80F5E3D7A0397C57A

0F5E3D7A0397C57A

You can download the GPG key or fetch it via the command-line:

curl -1sLf 'https://packages.konghq.com/public/kuma-legacy/gpg.0F5E3D7A0397C57A.key'

Public RSA Key

RSA-based keys/signatures are used by:

The public RSA key for the kong/kuma-legacy is:

It has the following long (16 bytes) and short (8 bytes) fingerprints:

6E468C6BA3912A13C999D78DCD255C88

C999D78DCD255C88

You can download the RSA key or fetch it via the command-line:

curl -1sLf 'https://packages.konghq.com/public/kuma-legacy/rsa.C999D78DCD255C88.key'

Public ECDSA Key

ECDSA-based keys/signatures are used by:

The public ECDSA OpenSSH key for the kong/kuma-legacy is:

-----BEGIN PUBLIC KEY-----
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEqD28DoCJYRM+nrs+nPblcENvoMMS
R9XFpL8aDsKaIEJJ3sIdXXKwpsYDB05iM3hQoY87dzx7YGJMQkXsV5q0YQ==
-----END PUBLIC KEY-----

It has the following long (16 bytes) and short (8 bytes) fingerprints:

75629A982A51E23649D4B162CF037104

49D4B162CF037104

You can download the ECDSA key or fetch it via the command-line:

curl -1sLf 'https://packages.konghq.com/public/kuma-legacy/ecdsa.49D4B162CF037104.key'

Please note however that the NPM client does not require this key to be installed system-wide in order to allow for package verification - NPM tooling will handle keys automatically.

Public Ed25519 Key

Ed25519-based keys/signatures are used by:

The public Ed25519 key for the kong/kuma-legacy is:

-----BEGIN PUBLIC KEY-----
MCowBQYDK2VwAyEAV3eBpUsrA97AHcOPCYsljreeyaLl+Hy5Fu+snLuM66g=
-----END PUBLIC KEY-----

It has the following long (32 bytes) and short (8 bytes) fingerprints:

A4296247A3DAB07ABB0D2454C0C0817BFCD3BEFD0C6D2D07C35B925D74B8DFD5

C35B925D74B8DFD5

You can download the Ed25519 key or fetch it via the command-line:

curl -1sLf 'https://packages.konghq.com/public/kuma-legacy/ed25519.C35B925D74B8DFD5.key'

For Nix, add this name:base64 line to trusted-public-keys:

kong-kuma-legacy-12812:V3eBpUsrA97AHcOPCYsljreeyaLl+Hy5Fu+snLuM66g=

Need Help?

If you couldn't find what you needed in our documentation, then you can always chat to a member of our team instead. It's our mission to be your dedicated off-site team for package management, and we mean it. Come and chat with us, anytime.

Alpine Public Key Installation

The following instructions are for Alpine (e.g. apk) packages or compatible.

Automated Installation (Bash)

If you installed the kong/kuma-legacy repository by following one of the repository installation instructions then you don't need take any further action. The RSA key should already have been installed alongside the repository.

Manual Installation

If you'd like to manually install the RSA key, you can utilise curl to retrieve the RSA key and install it by executing:

curl -1sLf 'https://packages.konghq.com/public/kuma-legacy/rsa.C999D78DCD255C88.key' >/etc/apk/keys/kuma-legacy@kong-C999D78DCD255C88.rsa.pub

Or you can add it directly without curl by executing:

sudo cat >/etc/apk/keys/kuma-legacy@kong-C999D78DCD255C88.rsa.pub <<EOF
    -----BEGIN PUBLIC KEY-----
MIIBojANBgkqhkiG9w0BAQEFAAOCAY8AMIIBigKCAYEAr6bwCLa5h3VlDUPeu+P4
I35hNOxqbGQK8xn6qeiBcvXDLHmIWX+6D8miDt0lnL6r99d7lTzMs7q75ZpU75jB
LfK7BshgZAIHw35q6qgpcxJBaXjaRMIbaDhlOHxSmMMKjFWt0B9BNB9vhpUyuWgr
ixzrS708m/SRA0vAD/UIKL1mYjXrXCwDg/933AYQs4McDD13yAapRcI2F3O0x5Cb
wraZl95ytzUO0/lEXYk/WGYmM1tsFwJhtp1feDoLhGP4QNRdUVR8ypHA41gaKqjp
dGCFWd23KMMts3N8TlFF85+W0HYjusL5yc25V/Py+aNk2N8GM7rNAh0lkWV/AZ8m
+P5C7ScqH1ldBokpOYpQNeuHW9AFMqSyeznOV8s+GYI3avVT5HlJI1f2EBYQMAca
pHURdOly5cRq4pYqqc4bHMv6cYh49MS457x5Mnm7Y+WyuSGrbuLWLm5JieI6g9ar
jvbAsSjnKKHJnFiT3y/plC9v/31U3Mwn+eHAXWqS6v2xAgMBAAE=
-----END PUBLIC KEY-----
    EOF

Removing Installation / Uninstalling

If you want to remove the public RSA key for the kong/kuma-legacy repository then you can do so by executing the following:

sudo rm -f /etc/apk/keys/kuma-legacy@kong-C999D78DCD255C88.rsa.pub

Note: Don't do this if you currently have the repository installed and wish to continue using it. If you remove the key the next fetch will fail.

Viewing Installed Keys

If you want to verify that a RSA public key has been installed or removed, you can view the list of all installed keys by executing:

ls -la /etc/apk/keys/

What's this page? All Cloudsmith repositories and packages are signed using GPG, RSA or ECDSA keys where supported. Signatures and checksums provide reliable mechanisms to ensure that the packages that you download/install are neither corrupt nor modified. GPG is generally preferred, but RSA or ECDSA is used for some package formats (such as Alpine or NPM). Learn more in the signing keys documentation.

Table of Contents