Fix #187: fix redis-session.ini permission denied

[antoinetran]

Description of the change

Following closure of #717 because of target branch develop deleted. This PullRequest targets main branch now.

Benefits

Possible drawbacks

Applicable issues

• fixes #

Additional information

Checklist

• I have read the CONTRIBUTING.md doc.
• DCO has been signed off on the commit.
• Chart version bumped in Chart.yaml according to semver.
• (optional) Parameters are documented in the README.md

[lindhe]

 ## Applicable issues
 
- - fixes #
+ - fixes #187

[95gabor]

Thanks for your work on this! I’m also looking forward to this PR being merged.
Could you please also include the cronjob init container?

[antoinetran]

Thanks for your work on this! I’m also looking forward to this PR being merged. Could you please also include the cronjob init container?

The only issue with my workaround is that it is a workaround. I created an issue aptible/supercronic#213 so that there is at least an official image so that nextcloud can rely on it.

[antoinetran]

Thanks for your work on this! I’m also looking forward to this PR being merged. Could you please also include the cronjob init container?

@95gabor I think we should separate this pull request from the cron issue. Because it will take some time to have a real fix in busybox cron implementation.

[antoinetran]

Anything preventing this pull request from being merged now?

[anthonymag]

Hey @antoinetran thanks for this, I have this working on mine in the meantime as an extraInitContainer.
One thing that's missing is adding the securityContext to the initContainer as well. If the redis-session.ini is created as a different user, the main nextcloud container will still get a permission denied when it tries to use it. I just hit this myself.

[antoinetran]

Hey @antoinetran thanks for this, I have this working on mine in the meantime as an extraInitContainer. One thing that's missing is adding the securityContext to the initContainer as well. If the redis-session.ini is created as a different user, the main nextcloud container will still get a permission denied when it tries to use it. I just hit this myself.

Hi, thanks for the feedback! You are correct, I added the SCC and resource as configurable. The SCC will take the same as the nextcloud SCC, because it uses the same image. Also normally the default nextcloud images (apache / fpm) are as root by default, so the default SCC configuration here should work.

[antoinetran]

Hi @varet80 , I just rebased on main and force push to get a clean history. Please feel free to comment.

[antoinetran]

hi, is-there anything I can do to change the progress?

[anthonymag]

Hi @varet80 , are you or someone on the team available to review this PR?

[varet80]

Good day,
I cannot understand how this went sideways. Sorry for that.

Can you resolve conflicts, fix version and request review?
Thank you

[antoinetran]

Good day, I cannot understand how this went sideways. Sorry for that.

Can you resolve conflicts, fix version and request review? Thank you

Yes no problem. I just did it.