ef4d14bb18
Current ingress relation only routes unit to requirer's leader. Ingress V2 fixes that issue. Change-Id: Idf3d46c89e366314d34553ad89422339e64b84c8 |
||
---|---|---|
.. | ||
lib/charms | ||
src | ||
tests | ||
.flake8 | ||
.gitignore | ||
.gitreview | ||
.jujuignore | ||
.stestr.conf | ||
.zuul.yaml | ||
actions.yaml | ||
charmcraft.yaml | ||
config.yaml | ||
CONTRIBUTING.md | ||
fetch-libs.sh | ||
LICENSE | ||
metadata.yaml | ||
osci.yaml | ||
pyproject.toml | ||
README.md | ||
rename.sh | ||
requirements.txt | ||
test-requirements.txt | ||
tox.ini |
keystone-k8s
Description
keystone-k8s is an operator to manage the Keystone identity service on a Kubernetes based environment.
Usage
Deployment
keystone-k8s is deployed using below command:
juju deploy keystone-k8s keystone --trust
Now connect the keystone operator to an existing database.
juju relate mysql:database keystone:database
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 keystone
. If the charm is not
deployed then see file actions.yaml
.
Relations
The charm supports the following relations. They are primarily of use to developers:
-
identity-credentials
: Used by charms to obtain Keystone credentials without creating a service catalogue entry. Set 'username' only on the relation and Keystone will set defaults and return authentication details. Possible relation settings:username
: Username to be created.project
: Project (tenant) name to be created. Defaults to service's project.domain
: Keystone v3 domain the user will be created in. Defaults to the Default domain.
-
identity-service
: Used by API endpoints to request an entry in the Keystone service catalogue and the endpoint template catalogue.When a relation is established Keystone receives the following data from the requesting API endpoint:
service_name
region
public_url
admin_url
internal_url
Keystone verifies that the requested service is supported (the list of supported services should remain updated). The following will occur for a supported service:
- an entry in the service catalogue is created
- an endpoint template is created
- an admin token is generated.
The API endpoint receives the token and is informed of the ports that Keystone is listening on.
OCI Images
The charm by default uses ghcr.io/openstack-snaps/keystone:2023.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.