Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Jobservice cannot run replicated with RWO PVCs #18067

Closed
zyyw opened this issue Jan 5, 2023 · 0 comments · Fixed by #18107
Closed

Jobservice cannot run replicated with RWO PVCs #18067

zyyw opened this issue Jan 5, 2023 · 0 comments · Fixed by #18107
Assignees
@wy65701436 @zyyw @chlins
Labels
target/2.8.0

Comments

@zyyw
Copy link
Contributor

zyyw commented Jan 5, 2023

There is reported issue in harbor-helm repo saying that "Jobservice cannot run replicated with RWO PVCs":

We are using this chart to deploy harbor on a kubernetes cluster that only supports ReadWriteOnce for persistent volumes. Currently we are running 3 replicas for the jobservice component. We are using the database JobLogger and S3 as storage backend for the registry.
When installing or updating to chart version 1.10.0 (Harbor 2.6) only one jobservice pod will become available, while the others stay in "ContainerCreating" phase. This happens because they all try to mount the same new scan data export volume.

More details:

Shall we investigate the feasibility of storing scan data exports in the database or go through the Possible solutions mentioned in the above harbor-helm issue 1320.
@chlins chlins mentioned this issue Jan 17, 2023
Merged
5 tasks
chlins added a commit to chlins/harbor that referenced this issue Jan 17, 2023
@chlins
fix: remove the scan exports volume
359ac25 
1. Change the Export CVE temporary file directory to /tmp.
2. Remove the scan data export volume in Dockerfile and docker-compose
   yaml.

Fixes: goharbor#18067

Signed-off-by: chlins <chenyuzh@vmware.com>
chlins added a commit to chlins/harbor that referenced this issue Jan 17, 2023
@chlins
fix: remove the scan exports volume
0e26e17 
1. Change the Export CVE temporary file directory to /tmp.
2. Remove the scan data export volume in Dockerfile and docker-compose
   yaml.

Fixes: goharbor#18067

Signed-off-by: chlins <chenyuzh@vmware.com>
@chlins chlins mentioned this issue Jan 17, 2023
Merged
5 tasks
chlins added a commit to chlins/harbor that referenced this issue Jan 17, 2023
@chlins
fix: remove the scan exports volume
1c01209 
1. Change the Export CVE temporary file directory to /tmp.
2. Remove the scan data export volume in Dockerfile and docker-compose
   yaml.

Fixes: goharbor#18067

Signed-off-by: chlins <chenyuzh@vmware.com>
@chlins chlins mentioned this issue Jan 17, 2023
Merged
5 tasks
chlins added a commit to chlins/harbor that referenced this issue Jan 31, 2023
@chlins
fix: remove the scan exports volume
100dca4 
1. Change the Export CVE temporary file directory to /tmp.
2. Remove the scan data export volume in Dockerfile and docker-compose
   yaml.

Fixes: goharbor#18067

Signed-off-by: chlins <chenyuzh@vmware.com>
chlins added a commit to chlins/harbor that referenced this issue Jan 31, 2023
@chlins
fix: remove the scan exports volume
a1ed07c 
1. Change the Export CVE temporary file directory to /tmp.
2. Remove the scan data export volume in Dockerfile and docker-compose
   yaml.

Fixes: goharbor#18067

Signed-off-by: chlins <chenyuzh@vmware.com>
chlins added a commit that referenced this issue Jan 31, 2023
@chlins
fix: remove the scan exports volume (#18109)
771373c 
1. Change the Export CVE temporary file directory to /tmp.
2. Remove the scan data export volume in Dockerfile and docker-compose
   yaml.

Fixes: #18067

Signed-off-by: chlins <chenyuzh@vmware.com>
chlins added a commit to chlins/harbor that referenced this issue Jan 31, 2023
@chlins
fix: remove the scan exports volume
64b247e 
1. Change the Export CVE temporary file directory to /tmp.
2. Remove the scan data export volume in Dockerfile and docker-compose
   yaml.

Fixes: goharbor#18067

Signed-off-by: chlins <chenyuzh@vmware.com>
chlins added a commit that referenced this issue Jan 31, 2023
@chlins
fix: remove the scan exports volume (#18107)
bfe4362 
1. Change the Export CVE temporary file directory to /tmp.
2. Remove the scan data export volume in Dockerfile and docker-compose
   yaml.

Fixes: #18067

Signed-off-by: chlins <chenyuzh@vmware.com>
AllForNothing pushed a commit to AllForNothing/harbor that referenced this issue Feb 3, 2023
@chlins
fix: remove the scan exports volume (goharbor#18107)
aa0f129 
1. Change the Export CVE temporary file directory to /tmp.
2. Remove the scan data export volume in Dockerfile and docker-compose
   yaml.

Fixes: goharbor#18067

Signed-off-by: chlins <chenyuzh@vmware.com>
AllForNothing pushed a commit to AllForNothing/harbor that referenced this issue Feb 3, 2023
@chlins
fix: remove the scan exports volume
747d420 
1. Change the Export CVE temporary file directory to /tmp.
2. Remove the scan data export volume in Dockerfile and docker-compose
   yaml.

Fixes: goharbor#18067

Signed-off-by: chlins <chenyuzh@vmware.com>
chlins added a commit to chlins/harbor that referenced this issue Feb 6, 2023
@chlins
fix: remove the scan exports volume
9b7ddaa 
1. Change the Export CVE temporary file directory to /tmp.
2. Remove the scan data export volume in Dockerfile and docker-compose
   yaml.

Fixes: goharbor#18067

Signed-off-by: chlins <chenyuzh@vmware.com>
chlins added a commit that referenced this issue Feb 6, 2023
@chlins
fix: remove the scan exports volume (#18108)
6465673 
1. Change the Export CVE temporary file directory to /tmp.
2. Remove the scan data export volume in Dockerfile and docker-compose
   yaml.

Fixes: #18067

Signed-off-by: chlins <chenyuzh@vmware.com>
tpoxa pushed a commit to container-registry/harbor that referenced this issue Feb 8, 2023
@chlins
fix: remove the scan exports volume (goharbor#18107)
e4f07a3 
1. Change the Export CVE temporary file directory to /tmp.
2. Remove the scan data export volume in Dockerfile and docker-compose
   yaml.

Fixes: goharbor#18067

Signed-off-by: chlins <chenyuzh@vmware.com>
Signed-off-by: Maksym <maksym@container-registry.com>
mcsage pushed a commit to mcsage/harbor that referenced this issue Feb 16, 2023
@chlins
fix: remove the scan exports volume (goharbor#18107)
1bda94c 
1. Change the Export CVE temporary file directory to /tmp.
2. Remove the scan data export volume in Dockerfile and docker-compose
   yaml.

Fixes: goharbor#18067

Signed-off-by: chlins <chenyuzh@vmware.com>
Signed-off-by: Stephan Hohn <stephan.hohn@tech11.com>
sebglon pushed a commit to sebglon/harbor that referenced this issue Mar 6, 2023
@chlins @sebglon
fix: remove the scan exports volume (goharbor#18107)
14d00bf 
1. Change the Export CVE temporary file directory to /tmp.
2. Remove the scan data export volume in Dockerfile and docker-compose
   yaml.

Fixes: goharbor#18067

Signed-off-by: chlins <chenyuzh@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wy65701436 wy65701436

@zyyw zyyw

@chlins chlins

Labels
target/2.8.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: remove the scan exports volume chlins/harbor
4 participants
@stonezdj @wy65701436 @zyyw @chlins