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.

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 helm chart to use nextcloud 21 #106

Closed
ntimo opened this issue Apr 11, 2021 · 10 comments
Closed

Update helm chart to use nextcloud 21 #106

ntimo opened this issue Apr 11, 2021 · 10 comments

Comments

@ntimo
Copy link

ntimo commented Apr 11, 2021

Hello,
currently the helm chart uses Nextcloud version 19, but the latest released version of Nextcloud is 21. I would suggest updating the helm chart to support Nextcloud 21.

@ch8zer
Copy link

ch8zer commented Apr 18, 2021

I second this, it would be nice to upgrade to the latest version

@marqsbla
Copy link

+1

@ngrigoriev
Copy link

By the way, I have successfully installed Nextcloud 21.0.1 with this chart by just changing the image tag.

@ch8zer
Copy link

ch8zer commented May 4, 2021

I haven't, filed a ticket: #112

@sign-out
Copy link

sign-out commented Aug 1, 2021

+1 i would help but um a noob nob and dont know how yet

@aliocha
Copy link

aliocha commented Aug 2, 2021

+1 is there any plan to update this chart to use the latest stable release of nextcloud?
Last time i tried to use a different docker image by overriding my values.yaml, i completly broke my deployment.

@Grennith
Copy link

Grennith commented Aug 4, 2021

I haven't, filed a ticket: #112

That helped with getting rid of the warning, thanks. What was also needed in my case (moving from 19.0.4): Set a Redis password. Without it, nextcloud attempted to AUTH without a password - obviously failing to do so as it was unexpected by Redis.
I am now running 21.0.3 trying to get rid of the warnings in regards to security

@varac
Copy link
Contributor

varac commented Aug 23, 2021

NC21 is already the default, I think this issue can be closed (or renamed to default to NC22)

@huerlisi
Copy link

It's already NC22 now. Upgraded without any issues.

Can be closed:-)

@jessebot
Copy link
Collaborator

Yeah, I think this can be closed to clear up some clutter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests