jfrog
After mounting S3V3 as persistency JCR stops showing onboarding page
Is this a request for help?: Yes
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
Version of Helm and Kubernetes: 3.3.0
Which chart: artifactory-jcr
What happened: When configured S3 V3 as persistency layer after first login I don't get onboarding page and JCR says that EULA is not signed then I can't use it fully.
What you expected to happen: Normal configuration or possibility to configure those steps from chart values
How to reproduce it (as minimally and precisely as possible): configure s3 v3 persistency type
Anything else we need to know: don't know
found way to fix it. Config map needed:
---
apiVersion: v1
kind: ConfigMap
metadata:
name: artifactory-config
namespace: artifactory
data:
artifactory.config.import.yml: |
GeneralConfiguration:
eula:
accepted: true
OnboardingConfiguration:
repoTypes:
- docker
- helm
and then in artifactory.artifactory.configMapName: artifactory-config
it works for me - even will be good if it will work in all storage cases same way.
@kivio Can you share the reproducible steps (helm commands and values.yaml file) along with chart version
I don't think it has anything to do with S3v3... I can reproduce this in minikube, with all the default values..
Steps to reproduce:
-
helm upgrade --install jcr jfrog/artifactory-jcr - (wait till it is running)
-
kubectl port-forward jcr-artifactory-0 8082 - VISIT: http://127.0.0.1:8082
You can login as admin/password, but no onboarding wizard comes up, it takes you to the "create a repo" step, which per the docs is at the end of the wizard?
