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.4.0

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.4.0
File Size Uploaded Provenance Actions
canonical_service_mesh-0.4.0.tar.gz 82.3 kB With provenance Details for canonical_service_mesh-0.4.0.tar.gz

Built distribution (wheel)

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

Total release size: 126.1 kB

Release files / canonical_service_mesh-0.4.0.tar.gz

Download URL canonical_service_mesh-0.4.0.tar.gz
Size 82.3 kB
Tags Source
SHA-256 checksum
How to use checksums
7f96841a335610ea13c08af3e67d4433ac4cd44c0d07fbb6008e8a998795b0d5
BLAKE2b-256 checksum
How to use checksums
e77fb4227b9e17bd486a8fd99171ae4a865a570ecca531906bfc86849849f765
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 30, 2026.

Transparency log

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

Download URL canonical_service_mesh-0.4.0-py3-none-any.whl
Size 43.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4e46df9fe1a5f344164a035048b122a9c7779bbc484901f03162c5a4b414cff1
BLAKE2b-256 checksum
How to use checksums
7dc4edf54e295e6aa4da46f4296af9418a3430a43ba7909eb3a0846aabb8ccf7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 30, 2026.

Transparency log

Security for canonical-service-mesh 0.4.0

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for canonical_service_mesh-0.4.0.tar.gz

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 30, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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