Interface catalogue
Interfaces describe the relation between two charms.
- auth_proxy v0 (draft): Configure an Identity and Access Proxy.
- azure_service_principal v0 (draft): Interact with Microsoft Entra ID using service principal credentials.
- azure_storage v0 (draft): Access Azure Blob Storage and Data Lake Storage (Gen 2).
- certificate_transfer v1 (draft): Receive public or CA certificates.
- cloudflared_route v0 (draft): Configure a cloudflared tunnel.
- connect_client v0 (draft): Interact with Kafka Connect clusters.
- cos_agent v0 (published): Machine-charm-specific interface for managing multiple observability-related data streams.
- database_backup v0 (draft): Manage database backup and restore operations.
- dns_record v0 (draft): Create and manage DNS records.
- etcd_client v0 (draft): Access etcd clusters with credentials and TLS configuration.
- filesystem_info v0 (draft): Export mount information about shared filesystems.
- fiveg_core_gnb v0 (draft)
- fiveg_f1 v0 (draft)
- fiveg_gnb_identity v0 (draft)
- fiveg_n2 v0 (draft)
- fiveg_n3 v0 (draft)
- fiveg_n4 v0 (draft)
- fiveg_nrf v0 (draft)
- fiveg_rfsim v0 (draft)
- forward_auth v0 (draft)
- grafana_auth v0 (draft): Provide authentication configuration for Grafana.
- grafana_datasource v0 (published): Provide Grafana data source servers.
- grafana_datasource_exchange v0 (draft): Share UIDs for Grafana datasources between charms.
- hydra_endpoints v0 (draft)
- ingress v2 (published)
- ingress_per_unit v0 (published)
- ip_router v0 (draft)
- istio_metadata v0 (draft): Share Istio installation metadata between charms.
- jwt v0 (draft): Provide and consume JSON Web Token configuration.
- k8s-service v0 (published)
- k8s_backup_target v0 (draft): Configure Kubernetes backup target specifications.
- kafka_client v0 (draft): Interact with Kafka clusters as a client.
- karapace_client v0 (draft): Access Karapace schema registry services.
- kratos_external_idp v0 (draft)
- kratos_info v0 (published)
- kubeflow_dashboard_links v0 (draft)
- ldap v0 (draft): Configure and connect to a Lightweight Directory Access Protocol (LDAP) server.
- litmus_auth v0 (draft): Exchange gRPC server endpoints for communication between Litmus auth and backend charms.
- login_ui_endpoints v0 (draft)
- milter v0 (published): Provide or consume a mail filter.
- mimir_cluster v0 (draft): Mimir coordinator and worker charm communication.
- mongodb_client v0 (draft): Access MongoDB databases with unique credentials.
- mysql_client v0 (published): Access MySQL databases with unique credentials.
- nginx-route v0 (draft): Create an Nginx ingress resource in a Kubernetes cluster.
- oauth v0 (draft): Connect to an OAuth2/OIDC Provider.
- opencti_connector v0 (published): Connect a single OpenCTI provider to one or more OpenCTI connectors.
- openfga v1 (published): Set up and connect to an OpenFGA store.
- opensearch_client v0 (draft): Access OpenSearch and ElasticSearch clusters.
- postgresql_client v0 (draft): Access PostgreSQL databases with unique credentials.
- profiling v0 (draft)
- prometheus_remote_write v0 (published): Write Prometheus metrics to remote endpoint.
- prometheus_scrape v0 (published): Configure Prometheus scraping jobs.
- pyroscope_cluster v0 (draft): Pyroscope coordinator and worker charm communication.
- s3 v1 (draft)
- saml v0 (published): Authenticate users with SAML.
- sdcore_config v0 (draft)
- sdcore_management v0 (draft)
- smtp v0 (published): Connect to a SMTP server.
- spark_service_account v0 (draft)
- tempo_cluster v1 (published): Tempo coordinator and worker charm communication.
- tls-certificates v1 (published): Securely request TLS certificates.
- tracing v2 (published): Request endpoints for pushing trace data.
- valkey_client v1 (published): Access Valkey databases with credentials and TLS configuration.
- vault-autounseal v0 (draft)
- vault-kv v0 (draft): Securely share Vault credentials to interact with the Vault Key-Value (KV) backend.
- velero_backup_config v0 (draft): Configure Kubernetes backup requirements for Velero.
- wazuh_api_client v0 (draft): The `wazuh_api_client` interface allows charms to connect to a Wazuh server. The provider charm manages access to the server, securely providing credentials and endpoints to the requirer charms.
- zookeeper v0 (draft)