Skip to main content

canonical_service_mesh

A shared utility library for the Charmed Service Mesh ecosystem.

Purpose

The Charmed Service Mesh ecosystem will contain charms that integrate service mesh technologies into the Juju ecosystem. These charms and their interface libraries share a significant amount of common code: Pydantic models for Kubernetes resource creation and service mesh CRD resources, lightkube-based resource management, label generation and authorization policies etc.

This package is the single home for all of that shared utility code. By centralizing it here, every charm and interface library depends on one well-maintained package instead of copying code between repositories or pulling from multiple helper packages.

Ecosystem

The ecosystem has three layers:

  1. This package (canonical_service_mesh) provides models, resource managers, and helpers. It has no knowledge of Juju relations or charm lifecycle, which keeps it testable and reusable.
  2. Interface libraries (via the charmlibs monorepo) define the relation databag schemas and the interface classes. They import from this package.
  3. Charms contain purely the charm specific logic and consume the interface and the canonical_service_mesh libraries.

Package structure

enums

Shared enumerations used across the ecosystem.

models

Pydantic models for Kubernetes and service mesh resources. The top-level models module contains generic Kubernetes Gateway API resource models. The models.istio subpackage contains Istio-specific CRD specs for authorization policies and request authentication.

utils

Helper functions for Kubernetes label generation, Juju identity resolution, and service mesh specific operations like label ConfigMap reconciliation and policy resource construction.

k8s

Kubernetes resource management built on lightkube. The k8s.resource_manager subpackage provides declarative resource lifecycle management with label-based ownership, policy resource management, and batch operations. The k8s.types subpackage defines lightkube type aliases and custom resource definitions.

Metadata

Release files for canonical-service-mesh 0.3.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for canonical-service-mesh 0.3.1
File Size Uploaded
canonical_service_mesh-0.3.1.tar.gz 81.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for canonical-service-mesh 0.3.1
File Interpreter ABI Platform
canonical_service_mesh-0.3.1-py3-none-any.whl Python 3 none any Details

Total release size: 124.7 kB

Release files / canonical_service_mesh-0.3.1.tar.gz

Download URL canonical_service_mesh-0.3.1.tar.gz
Size 81.2 kB
Tags Source
SHA-256 checksum
How to use checksums
d41e09cfa7ab3be6aac8f6a72830414deb1c1430c940f9d01d1ea6ab363ce712
BLAKE2b-256 checksum
How to use checksums
1190f984c848e65397b5ed9460cc44e26d391994b1f6cd41d6f038e9fada266e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.

Transparency log

Release files / canonical_service_mesh-0.3.1-py3-none-any.whl

Download URL canonical_service_mesh-0.3.1-py3-none-any.whl
Size 43.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6ae1bfaa54f157ba0880a33cd5711b9a0dd532b1245a453278caab04a51fd3e0
BLAKE2b-256 checksum
How to use checksums
7260184d231560ffc22bf0a93a75907318523887bc161778df944d5153a0dcd3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.3.1 This release

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.0

2 release files

0.0.2

2 release files

0.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page