JFrog Container Registry on Kubernetes returns 404 on UI endpoint

Looks like your port configuration is missing some changes.

1. You need to expose port 8082 in the jcr container, which is now the main UI port

2. Once port is exposed, you should add this port to your service.

So your revised yaml should look something like (Deployment and Service):

apiVersion: extensions/v1beta1kind: Deploymentmetadata:  name: jcr  namespace: <REDACTED>spec:  replicas: 1  template:    metadata:      labels:        app: jcr    spec:      containers:        - name: jcr          image: docker.bintray.io/jfrog/artifactory-jcr:latest          ports:            - containerPort: 8081            - containerPort: 8082          volumeMounts:            - name: jcr-data              mountPath: /jcr-data      volumes:        - name: jcr-data          persistentVolumeClaim:            claimName: jcr-data      securityContext:        fsGroup: 2000---apiVersion: v1kind: PersistentVolumeClaimmetadata:  name: jcr-dataspec:  accessModes:    - ReadWriteOnce  resources:    requests:      storage: 10Gi---apiVersion: v1kind: Servicemetadata:  name: jcr  namespace: <REDACTED>  annotations:      prometheus.io/scrape: 'true'      prometheus.io/path:   /      prometheus.io/port:   '8081'spec:  selector:     app: jcr  ports:    - port: 80      targetPort: 8082    - port: 8081      targetPort: 8081  sessionAffinity: None  type: ClusterIP

Notice I left 8081 open, which allows for direct access to Artifactory if needed for better performance (Artifactory is now running behind a router service).

NOTE - I recommend using the official JFrog Container Registry Helm chart, which greatly simplifies the process of configuring and managing your JCR deployment lifecycle.