Files

Guillaume Boutry b2f8389a54 Update to epoxy

Ensure testing uses new RBAC, defaults in 2025.1.

Change-Id: I172ecebbcb78135a999499fa6382b59ef1af3ad9
Signed-off-by: Guillaume Boutry <guillaume.boutry@canonical.com>

2025-04-30 08:44:20 +02:00

2.1 KiB

Raw Blame History

aodh-k8s

Description

aodh-k8s is an operator to manage the alarm services aodh api, aodh evaluator, aodh notifier, aodh listener and aodh expirer on a Kubernetes based environment.

Usage

Deployment

aodh-k8s is deployed using below command:

juju deploy aodh-k8s aodh --trust

Now connect the aodh operator to existing database, keystone identity, and rabbitmq operators:

juju relate mysql:database aodh:database
juju relate keystone:identity-service aodh:identity-service
juju relate rabbitmq:amqp aodh:amqp

Configuration

This section covers common and/or important configuration options. See file config.yaml for the full list of options, along with their descriptions and default values. See the Juju documentation for details on configuring applications.

Actions

This section covers Juju actions supported by the charm. Actions allow specific operations to be performed on a per-unit basis. To display action descriptions run juju actions aodh. If the charm is not deployed then see file actions.yaml.

Relations

aodh-k8s requires the following relations:

database: To connect to MySQL identity-service: To register endpoints in Keystone ingress-internal: To expose service on underlying internal network ingress-public: To expose service on public network amqp: To connect to Rabbitmq

OCI Images

The charm by default uses following images:

ghcr.io/canonical/aodh-consolidated:2025.1

Contributing

Please see the Juju SDK docs for guidelines on enhancements to this charm following best practice guidelines, and CONTRIBUTING.md for developer guidance.

Bugs

Please report bugs on Launchpad.

2.1 KiB Raw Blame History