You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry for my misunderstanding of the documentation, it works now.
This wasn't so clear from reading the "Configure database credentials in Helm with a pre-existing Kubernetes secret" section of Use an external database with Artifactory Helm installation
The appearance of a few tables made me quickly rule out problems related to the connection chain to the database.
So for the record, the complete configuration of the external database with external secret should look like this:
Is this a request for help?: YES
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
Version of Helm and Kubernetes:
Which chart: artifactory-oss-107.77.7.tgz
Which product license (Enterprise/Pro/oss): oss
JFrog support reference (if already raised with support team):
What happened:
Configuring a Postgresql External Database in Helm Chart values.yaml results in an infinite wait for the master key
pod-logs-details.txt
until CrashLoopBackOff
What you expected to happen:
The pod going to a Running State accessing and initializing the created Database in configured Postgresql DBMS.
How to reproduce it (as minimally and precisely as possible):
create and apply an "rds-artifactory" secret storing db-user, db-password and db-url.
apiVersion: v1
kind: Secret
metadata:
name: rds-artifactory
labels:
app: tools-artifactory
data:
db-user: zzzzzzzzzz=
db-password: xxxxxxxxxxx==
stringData:
db-url: "jdbc:postgresql://10.43.10.204:5432/artifactory"
Fetch, untar, and configure values.yaml in the Artifactory OSS Helm Chart :
configured-artifactory-oss.zip
Repackage and install
Anything else we need to know:
The pod seems to connect to the configured database since few tables are created :
Letting Helm create an Artifactory dedicated Postgresql DBMS and DB is working, master key is waited for some tries and finishes to be found.
The text was updated successfully, but these errors were encountered: