Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

katib-db can still be charmed-osm-mariadb-k8s #178

Open
DnPlas opened this issue Apr 15, 2024 · 1 comment
Open

katib-db can still be charmed-osm-mariadb-k8s #178

DnPlas opened this issue Apr 15, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@DnPlas
Copy link
Contributor

DnPlas commented Apr 15, 2024

Context

Since CKF 1.7, charmed-osm-mariadb-k8s was replaced with mysql-k8s, but the Katib charms are still integrated with it. We must ensure we remove this and only allow mysql-k8s as the DB.

What needs to get done

  1. Remove all traces of charmed-osm-mariadb-k8s from the charm code
  2. Remove all traces of charmed-osm-mariadb-k8s from the katib-db-manager integration tests
  3. Remove all traces of charmed-osm-mariadb-k8s from the metadata.yaml file

Definition of Done

The Katib charms are not integrated anymore with charmed-osm-mariadb-k8s

@DnPlas DnPlas added the enhancement New feature or request label Apr 15, 2024
Copy link

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5571.

This message was autogenerated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant