Closed chook closed 4 years ago
Hi @chook . Your observation is correct. This was a deliberate decision mostly for simplicity and backward compatibility for users of the Artifactory Docker image (which is very popular). We are looking into adding (optional) support for deploying as separate containers for K8s. This is still under a general idea. The benefits for separate containers are great, but business continuity and backward compatibility are very important in this case. I hope this answers your question.
It does! thanks for the quick and verbose response!
Is this a request for help?: Yes
Is this a BUG REPORT or FEATURE REQUEST? (choose one): Feature Request
Version of Helm and Kubernetes:
Which chart: artifactory
What happened: As opposed to xray/mission control, where the pod contains several containers, it seems artifactory brings 2 pods (artifactory / artifactory-nginx) where the artifactory-artifactory-0 pod contains only 1 container, the artifactory server.
What you expected to happen: I expect the pod to contains all services (UI, router, access, MDS, event) as described in https://www.jfrog.com/confluence/display/JFROG/System+Architecture
How to reproduce it (as minimally and precisely as possible): Install artifactory using helm
Anything else we need to know: no