History

Add ingress healthcheck params to charms

This change adds a healthcheck params dict to k8s charms for
use by traefik via the ingress relation. It contains a path,
interval, and timeout value. This allows traefik to detect
down nodes and remove them from the loadbalancer rotation.
Unless overridden in the charm, a default path of "/" is
passed in the ingress relation. Interval and timeout
are optional and will use default values of 30s and 5s,
respectively, unless overridden in the charm. Some charms
define a "/healthcheck" path in api-paste.ini which has been
used in place of the default "/" path.

Closes-Bug: #2077269
Change-Id: I355728f338e9a29fcf202cc629a977b49b2d8990

2025-03-12 15:02:20 -07:00

lib/charms/keystone_k8s

[keystone-k8s] Do not emit ready when permission issues on secret

2025-02-03 08:03:32 +00:00

src

Add ingress healthcheck params to charms

2025-03-12 15:02:20 -07:00

tests

Make ingress-internal mandatory relation

2024-12-09 18:43:30 +05:30

.gitignore

Refactor monorepo build-system

2024-07-08 21:51:09 +02:00

.sunbeam-build.yaml

Implement tracing

2024-07-31 11:57:32 +02:00

charmcraft.yaml

Derive mandatory relations from charmcraft.yaml

2025-02-03 15:23:59 +05:30

CONTRIBUTING.md

Update for 2024.1

2024-04-18 23:21:03 +00:00

LICENSE

Initial commit just to share

2021-07-06 11:54:32 -07:00

README.md

Update for 2024.1

2024-04-18 23:21:03 +00:00

rebuild

Cache secret for the duration of the hook

2024-05-30 18:06:25 +02:00

requirements.txt

Remove upper contraints on pydantic

2024-08-27 14:06:38 +05:30

README.md

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:
1. an entry in the service catalogue is created
2. an endpoint template is created
3. 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/canonical/keystone: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.