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
I can't find a way to supply the custom sidecar container with the admin token since the admin token can't be created until Artifactory has started once.
Why are you suggesting a pattern that can't be supported on a fresh kubernetes install?
To use the pattern currently suggested I need to start Artifactory once using helm, bootstrap an admin token that in turn can create a more permanent access token. Then when I have this new access token I need to redeploy the artifactory helm release with the custom sidecar container pattern. This is not a functional pattern for automatic deployments.
The text was updated successfully, but these errors were encountered:
Documentation was updated with a 2-step solution for your problem: helm install and then helm upgrade. Closing since it's an old issue. Please re-open if you still facing issues with the current instructions in README.
I can't find a way to supply the custom sidecar container with the admin token since the admin token can't be created until Artifactory has started once.
Why are you suggesting a pattern that can't be supported on a fresh kubernetes install?
To use the pattern currently suggested I need to start Artifactory once using helm, bootstrap an admin token that in turn can create a more permanent access token. Then when I have this new access token I need to redeploy the artifactory helm release with the custom sidecar container pattern. This is not a functional pattern for automatic deployments.
The text was updated successfully, but these errors were encountered: