43119913d6
* Make ingress-internal relation mandatory for charms instead of ingress-public * If ingress-public is not integrated, default public endpoint to internal endpoint Change-Id: Ibbc600b3dd53655f2160394d4717b75e14d63cf8
designate-k8s
Description
designate-k8s is an operator to manage the designate services on a Kubernetes based environment.
Usage
Deployment
designate-k8s is deployed using below command:
juju deploy designate-k8s designate --trust
Now connect the designate operator to existing database, messaging, keystone identity, and bind9 operators:
juju relate mysql:database designate:database
juju relate rabbitmq:amqp designate:amqp
juju relate keystone:identity-service designate:identity-service
juju relate bind9:dns-backend designate:dns-backend
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 designate. If the charm is not
deployed then see file actions.yaml.
Relations
designate-k8s requires the following relations:
database: To connect to MySQLamqp: To connect to RabbitMQidentity-service: To register endpoints in Keystoneingress-internal: To expose service on underlying internal networkingress-public: To expose service on public networkdns-backend: To register DNS records
OCI Images
The charm by default uses following images:
`ghcr.io/canonical/designate-consolidated:2024.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.