e911599abe
Charmcraft 3 moves towards a single charmcraft.yaml, this is needed for 24.04 migration. Change-Id: I743712752aaf37bf68730b64bd6c147dfad370e2 Signed-off-by: Guillaume Boutry <guillaume.boutry@canonical.com> |
||
---|---|---|
.. | ||
src | ||
tests/unit | ||
.sunbeam-build.yaml | ||
charmcraft.yaml | ||
CONTRIBUTING.md | ||
LICENSE | ||
README.md | ||
rebuild | ||
requirements.txt |
glance-k8s
Description
glance-k8s is an operator to manage the Glance image service on a Kubernetes based environment.
Usage
Deployment
glance-k8s is deployed using below command:
juju deploy glance-k8s glance --trust
Now connect the glance operator to an existing database, messaging and keystone identity operators:
juju relate mysql:database glance:database
juju relate rabbitmq:amqp glance:amqp
juju relate keystone:identity-service glance:identity-service
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 glance
. If the charm is not
deployed then see file actions.yaml
.
Relations
glance-k8s requires the following relations:
database
: To connect to MySQL
amqp
: To connect to RabbitMQ
identity-service
: To register endpoints in Keystone
ceph
: To connect to Ceph for image storage (optional)
ingress-internal
: To expose service on underlying internal network
ingress-public
: To expose service on public network
OCI Images
The charm by default uses ghcr.io/canonical/glance-api:2024.1
image.
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.