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
Which product license (Enterprise/Pro/oss): Enterprise
JFrog support reference (if already raised with support team): No
What happened: It is intensive to deploy artifactory using the above mentioned chart on an aws eks cluster using the command helm upgrade --namespace jfrog-artifactory-dev --install --values ./values.yaml --wait --debug devops ./artifactory-ha-107.71.5.tgz
Attached you will find the values.yaml file artifactory.zip.
What you expected to happen: Being able to have a functional instance of the artifactory-primary pod
How to reproduce it (as minimally and precisely as possible):
Download the attached artifactory.zip zip which will contain the values file and the artifactory chart (or download the official helm repo chart).
Create a clean namespace on your k8s cluster.
Run the command helm upgrade --namespace jfrog-artifactory-dev --install --values ./values.yaml --wait --debug devops ./artifactory-ha-107.71.5.tgz
Be sure to change the namespace name in the commands and the paths of the values and chart to your own.
Anything else we need to know: The installation being attempted is clean, that is, it is not trying to migrate from another version.
The text was updated successfully, but these errors were encountered:
juparog
changed the title
[ERROR] Binary not found at /opt/jfrog/router/app/router/bin/jf-router-linux-amd64
[FATAL] Cluster join: Failed resolving join key: failed resolving 'shared.security.joinKey' key; file does not exist: /opt/jfrog/router/var/etc/security/join.key
Feb 7, 2024
Is this a request for help?: Yes
Version of Helm and Kubernetes:
Which chart:
artifactory-ha-107.71.5.tgz
Which product license (Enterprise/Pro/oss): Enterprise
JFrog support reference (if already raised with support team): No
What happened: It is intensive to deploy artifactory using the above mentioned chart on an aws eks cluster using the command
helm upgrade --namespace jfrog-artifactory-dev --install --values ./values.yaml --wait --debug devops ./artifactory-ha-107.71.5.tgz
Failed pod
artifactory-ha-primary
:Error in container
router
:full log:
error.log
Attached you will find the values.yaml file artifactory.zip.
What you expected to happen: Being able to have a functional instance of the artifactory-primary pod
How to reproduce it (as minimally and precisely as possible):
helm upgrade --namespace jfrog-artifactory-dev --install --values ./values.yaml --wait --debug devops ./artifactory-ha-107.71.5.tgz
Anything else we need to know: The installation being attempted is clean, that is, it is not trying to migrate from another version.
The text was updated successfully, but these errors were encountered: