-
Notifications
You must be signed in to change notification settings - Fork 41
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.
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
🐛 Update PVC permissions #395
Conversation
7dcbaa3
to
1ea1216
Compare
1ea1216
to
90c6575
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks right to me, VISACK
656b949
to
82687cb
Compare
For whatever reason, when the cache PVC exists the Hub mounts it, so we must scale it down to allow the PVC to terminate so it can be recreated. |
934bc87
to
8804bac
Compare
Thinking about this more, since the Hub mounts the cache PVC if it exists we probably don't need to delete and recreate it. We should be able to chown everything like the others. It could however take awhile for the process to run, whereas deleting the cache and recreating it may be quicker. Curious what others opinions are with which way we should go. |
I think that deleting the cache should be fine and as you said would be quicker |
32f34a6
to
ff063a0
Compare
Signed-off-by: Jason Montleon <jmontleo@redhat.com>
ff063a0
to
d852448
Compare
Fixed the hard coded values in the initContainer causeing the e2e-api test failure. |
Signed-off-by: Jason Montleon <jmontleo@redhat.com> (cherry picked from commit a09410d)
No description provided.