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 mongodb chart version in deps #1071

Merged
merged 1 commit into from
Jul 4, 2019
Merged

Update mongodb chart version in deps #1071

merged 1 commit into from
Jul 4, 2019

Conversation

carrodher
Copy link
Contributor

@carrodher carrodher commented Jul 4, 2019

Signed-off-by: Carlos Rodriguez Hernandez crhernandez@bitnami.com

A new MongoDB version was released (helm/charts#15229) fixing an issue in some k8s cluster when IPv6 was disabled in the host, i.e #577.

This version also contains other changes in the chart (from MongoDB chart 5.0.0): https://github.com/helm/charts/tree/master/stable/mongodb#to-500

And also the bitnami/mongodb image was moved from nami to bash.

Signed-off-by: Carlos Rodriguez Hernandez <crhernandez@bitnami.com>
@carrodher carrodher changed the title Update mongodb in order to disable IPv6 by default Update mongodb chart version in deps Jul 4, 2019
Copy link
Contributor

@andresmgot andresmgot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have tested the upgrade and I didn't found any issue, thanks!

@andresmgot andresmgot merged commit 3b18120 into vmware-tanzu:master Jul 4, 2019
@sebastien-prudhomme
Copy link

It seems there is a breaking change: you need to remove mongodb.securityContext.enabled = false in the chart.

If not there is a permission problem when accessing the PV.

@andresmgot
Copy link
Contributor

andresmgot commented Jul 4, 2019

@sebastien-prudhomme what issue are you seeing? (I didn't notice anything when testing the new version)

By default Kubeapps doesn't deploy any PV, are you enabling persistence in MongoDB?

@sebastien-prudhomme
Copy link

@andresmgot Yes, i'm using persistence in MongoDB. I've tested with a fresh install and MongoDB keeps crashing because of permission denied.

The default value for security context is true in the MongoDB chart.

@sebastien-prudhomme
Copy link

@andresmgot i've just read that MongoDB is used as a cache...

@carrodher
Copy link
Contributor Author

carrodher commented Jul 4, 2019

In MongoDB chart, the securityContext was enabled in the 4.0.0 version: helm/charts#6809, as this PR is bumping the MongoDB chart from 4.9.0 to 6.0.0, those changes should be already included.

In the kubeapps values.yaml, the securityContext is disabled by default:

##
## MongoDB chart configuration
##
## https://github.com/helm/charts/blob/master/stable/mongodb/values.yaml
##
mongodb:
  # Kubeapps uses MongoDB as a cache and persistence is not required
  persistence:
    enabled: false
  # MongoDB credentials are handled by kubeapps to facilitate upgrades
  existingSecret: kubeapps-mongodb
  securityContext:
    enabled: false

Can you share with us the modifications you did in the values.yaml or by parameters? What k8s cluster are you using?

@sebastien-prudhomme
Copy link

@carrodher no need to investigate, i will suppress the persistence i added in MongoDB. This is the only modification i made.

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

Successfully merging this pull request may close these issues.

3 participants