-
Notifications
You must be signed in to change notification settings - Fork 15
Description
Hi all! 😄
Introduction
I am running open-source Quay 3.10.4 on Kubernetes 1.28.6 on-prem, deployed using my own k8s manifests. The registry is working fine so the problem is not related to the deployment.
Quay load image: quay.io/vchalla/quay-load:latest
As of running these scripts, I know you assume deployment on OpenShift, but the job itself does not contain any OpenShift related CRDs so I assumed it would work on bare k8s too.
I have set up the prerequisites including Elasticsearch and run the manifest with filled envs. Few of them that might be related below:
- name: ES_INDEX
value: "testing_1"
- name: PUSH_PULL_IMAGE
value: "alpine:edge"
- name: PUSH_PULL_ES_INDEX
value: "testing_pushpull_1"
- name: PUSH_PULL_NUMBERS
value: "10"
- name: TARGET_HIT_SIZE
value: "100"
- name: CONCURRENCY
value: "10"
- name: TEST_NAMESPACE
value: "quay"
- name: TEST_PHASES
value: "LOAD,RUN,DELETE"
I assumed the PUSH_PULL_IMAGE is the image that would be pushed and pulled from registry while testing.
The problem
After running these tests, the logs, including both Elasticsearch results, pod logs and Quay organization logs did not state anything about pushing or pulling images. The image of operations on organization is presented below:
There are also no logs pushed to the PUSH_PULL_ES_INDEX, just results in testing_1.
The phases that have run are all related to: teams, members, permissions, empty repositories.
Mentioned phases and job completed with no errors.
Expected behavior
- Phase of pushing and pulling images running, providing relative metrics, stored in ES
- Any logs in Quay stating that there were some pushes and pulls to/from repos
Thanks in advance for your feedback and I am open to cooperation.
