[MongoDB] Updatings values.yaml to enable monitoring and readme instructions

[grebois]

No description provided.

[sekka1]

Can we put everything below this in another .md file named updating_from_3.4.0.md and either link to it or just leave it as another file, because this chart will be updated again and the question is, do you keep the 3.4.0 update here or do you delete it or what? I think moving it out to another file now makes the main README.md clean and approachable.

[sekka1]

Didnt you have to edit the helm/stable chart and had a PR out? Where does that stand?

We should include that information with this type of PRs b/c it really depends on that to work.

This goes back to being able to consume this PR also, you should anticipate the clients questions and answer them before they ask. Because now im concerned that hasnt been merged and if i try this it would not work. Then that leads me to not trying it out right now (which i have set aside time for).

[sekka1]

@grebois there are some authentication issues when I upgraded:

  Warning  Unhealthy              39s   kubelet, ip-10-120-36-40.ec2.internal  Liveness probe failed: time="2018-07-25T19:32:37Z" level=error msg="Cannot connect to server using url mongodb://****:****@localhost:27017: server returned error on SASL authentication step: Authentication failed." source="connection.go:84"
time="2018-07-25T19:32:37Z" level=error msg="Can't connect to MongoDB: Cannot connect using uri: mongodb://metrics:password@localhost:27017" source="mongodb_exporter.go:104"

[sekka1]

PR for the helm/stable changes: helm/charts#6282