-
Notifications
You must be signed in to change notification settings - Fork 134
Use correct user for chmod command in cp-solr-xml init container #520
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
Conversation
cd5e897 to
12213dd
Compare
HoustonPutman
left a comment
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.
So I have a general question about this. We only specify the fsGroup by default. Do we not want to use the fsGroup provided in the custom PodSecurityContext?
|
@a-nych I'm pushing for a v0.7.0 release soon and it would be great to get this in there. Do you have any more info for my |
|
@a-nych pinging again so that we can get this in the upcoming release |
We do want to use the |
|
Hi,
Sorry for not responding - somehow missed these notifications. I will take
a thorough look at this tomorrow.
pon., 17 kwi 2023, 22:40 użytkownik Houston Putman ***@***.***>
napisał:
… So I have a general question about this. We only specify the fsGroup by
default
<https://github.com/apache/solr-operator/blob/main/controllers/util/solr_util.go#L479>.
Do we not want to use the fsGroup provided in the custom
PodSecurityContext?
We do want to use the fsGroup, since that is what is used for volumes. I
am also making sure to use 8983 as the default fsGroup when a custom
podSecurityContext is provided that doesn't use an fsGroup.
—
Reply to this email directly, view it on GitHub
<#520 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACHEM53E4JCDET5JXQ6UOCDXBWTEJANCNFSM6AAAAAAUDWCU54>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Thanks @a-nych , I'm planning on trying to cut the release by early afternoon tomorrow (EST timezone), so if you could get your review in early that'd be great! |
Resolves #519.