Skip to content
This repository has been archived by the owner on Nov 16, 2022. It is now read-only.

Add support for Microsoft SQL Server external database #439

Closed
oottka opened this issue Jan 3, 2022 · 2 comments
Closed

Add support for Microsoft SQL Server external database #439

oottka opened this issue Jan 3, 2022 · 2 comments

Comments

@oottka
Copy link

oottka commented Jan 3, 2022

Description

Add support for Microsoft SQL Server external databases to allow users to use MS SQL server if they prefer to do so. Currently the keycloak-operator only supports PostgreSQL external databases, but keycloak itself has support for many database engines.

Discussion

No response

Motivation

Currently keycloak-operator only supports PostgreSQL external databases. Providing a wider selection of options allows end users to choose the database they prefer. Support for MS SQL Server is already included in the Keycloak docker image.

Details

No response

@andreaTP
Copy link
Contributor

Hi @oottka , at this point the entire team is mostly busy building a new operator for Keycloak.
You can find the design proposal here: keycloak/keycloak-community#330 even there we are planning to support only PostgreSQL as it is the most widely used and the "opinionated" recommendation for a production environment.

Since in most Kubernetes offerings you have managed versions of Postgres, can you try to elaborate on the reasons behind this requirement?

@andreaTP
Copy link
Contributor

As this issue has been around for a long time we are closing this issue as out of date. If the issue is still valid, please verify with the latest version of the Keycloak operator, feel free to reopen and provide details to why it is still valid.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants