designate-k8s is an operator to manage the designate services on a Kubernetes based environment.
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
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.
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.
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
The charm by default uses following images:
`ghcr.io/canonical/designate-consolidated:2023.1`
Please see the Juju SDK docs for guidelines on enhancements to this charm following best practice guidelines, and CONTRIBUTING.md for developer guidance.
Please report bugs on Launchpad.