Repository navigation
Setup for autonomous DB based cluster in operator #11821
stevefan1999-personal
started this conversation in
Feedback
Replies: 1 comment
|
Here's a sample configuration for anyone interested: ---
apiVersion: k8s.keycloak.org/v2alpha1
kind: Keycloak
metadata:
name: keycloak
spec:
serverConfiguration:
- name: db
value: oracle
- name: db-url
value: jdbc:oracle:thin:@apps_medium?TNS_ADMIN=/etc/secrets/oracle/
- name: db-username
secret:
key: DB_USER
name: keycloak-db
- name: db-password
secret:
key: DB_PASSWORD
name: keycloak-db
unsupported:
podTemplate:
spec:
containers:
- volumeMounts:
- mountPath: /etc/secrets/oracle
name: oracle
readOnly: true
env:
- name: TNS_ADMIN
value: /etc/secrets/oracle/
volumes:
- name: oracle
secret:
secretName: oracle-appUnder my test this configuration successfully seeded a Keycloak X setup in my Oracle Autonomous DB. I do have to say it is weird to see everything in...Capital letters. This setting assumes Unfortunately, it seems like TNS_ADMIN environmental variable alone doesn't have any effects, so I also have to add it as a query option. So TNS_ADMIN as an environmental variable seems redundant (since the JDBC URL already specified the location) but is kept for defense purposes.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Code
Uh oh!
There was an error while loading. Please reload this page.
Oracle Autonomous DB is wallet based and hence needs TNS_ADMIN to be set to a certain path like
/etc/secrets/oracle/.I've uploaded the entire wallet to K8S as secret (as it definitely is), but there is no way to extract the secret to
/etc/secrets/oracle/without usingunsupportedAlso, it doesn't seems to have a way to set environmental variables without using
unsupportedin the operator as wellAll reactions