Comments (5)
Yes, this makes sense. When you set a password in neo4j 4.0+, it writes something to the system database. If you retain disk images between launches, then when your new database starts up, it will have the state on disk of the old system database, which of course has the old password.
This can be avoided several ways:
- When redeploying, use a different name
- Prior to redeploying, delete the PVCs associated with the old deploy
- Prior to redeploying, use other tooling to delete the /data/databases folders in the PVC mount point.
Unfortunately, as your'e describing this situation, it's working as intended. Helm doesn't auto-delete the PVCs associated with the install when you delete -- because the purpose of PVCs is to retain the data.
from neo4j-helm.
@moxious, yes indeed!
Sorry, I guess it was misinformation from my end.
But it is a good headsup if anyone stubble upon this in the future :)
Thanks a lot for your help
from neo4j-helm.
I'm not sure what's happening here because this bit is tested, and I can't reproduce.
Could you paste the exact command you're using to connect using this password, and what it's result is? Can you verify that the secret was installed in kubernetes, and that it's base64 decoded value is mySecretPassword?
A final thing to try is the default neo4j/neo4j. If the container failed to set your desired password (for some reason, which I doubt) then the password would be neo4j.
from neo4j-helm.
Any update here?
from neo4j-helm.
Hey @moxious , thanks for your quick response and sorry for my late one.
So I investigated a little bit more and it seems to be related to persistent volumes. If I install the chart once, delete it, and install it again with a different password it will keep the first password stored in the volume.
I don't know if that is an issue, but it might get people confused.
Here is what a I did to reproduce:
(make sure to clean up all the persistent volumes and claims using kubectl, or install chart with a different name)
- Install the chart for the first time:
helm install graphdb RELEASE_URL --set core.standalone=true --set acceptLicenseAgreement=yes --set neo4jPassword=pass1
- Run inside the cluster:
# this should work
curl http://neo4j:pass1@graphdb-neo4j-core-0.graphdb-neo4j.default.svc.cluster.local:7474/user/neo4j
- Delete chart:
helm delete graphdb --purge
- Install it again with different password:
helm install graphdb RELEASE_URL --set core.standalone=true --set acceptLicenseAgreement=yes --set neo4jPassword=pass2
- Run inside the cluster:
# this should not work
curl http://neo4j:pass2@graphdb-neo4j-core-0.graphdb-neo4j.default.svc.cluster.local:7474/user/neo4j
# this should work
curl http://neo4j:pass1@graphdb-neo4j-core-0.graphdb-neo4j.default.svc.cluster.local:7474/user/neo4j
from neo4j-helm.
Related Issues (20)
- Unable to set apoc.trigger.enabled in neo4j.conf HOT 1
- When using an older version of Neo4J (3.5) the latest changes in 4.3.2-1 chart cause startup errors
- Prometheus Endpoint fails
- Readiness probe prevents recovery
- Cannot create manual jobs from CronJob
- Specify a specific version of plugin to install HOT 1
- Add support for priority classes
- 3.5.30 - `neo4j-apoc-procedures/verison.json` for 3.5.30 not updated HOT 1
- Different nodeSelector, affinity and tolerations for core and readReplica
- Can't set toleration on the backup pods
- Can't change log format
- Issue when setting apoc export or import configurations HOT 5
- Please do not deprecate this chart!
- log4j version 2.17
- Neo4j 4.2.15 is not starting with helm version 4.2.14 HOT 2
- Entrypoint script has moved in 3.5.31 - no longer boots using Helm chart HOT 1
- Neo4j backup fails with azure-cli version 2.34.1
- Neo4j Installation Stuck due apoc plugin downloading failed.
- Wrong name with 4.4.10 release (neo4j-4.4.10.1.tgz)
- Deprecated API versions for Cronjob and PodDisruptionBudget
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from neo4j-helm.