Documentation and deployment scenario for cluster internal ssl #99
Conversation
| metadata: | ||
| name: cluster-internal-ssl-config | ||
| data: | ||
| NEO4J_unsupported_dbms_ssl_system_ignore__dot__files: "true" |
There was a problem hiding this comment.
does k8s do something funky with the volume mappings? Or why is this needed? I don't see any dotfiles in what you're mounting
There was a problem hiding this comment.
yes, yes it does, K8s creates the directories for the configmaps/secrets in its own locations and symlinks to them. It stores metadata in dot files which gets included.
The main reason for the wizardry is that they can update the symlink for a whole directory atomically at runtime if the ConfigMap or Secret is changed - obviously that's not relevant to Neo4j but there's no way to turn it off in K8s.
|
PR is on hold because it requires release of Neo4j 4.1.2 to work in all aspects. For this reason it won't be released as part of 4.1.1-*. But ready for merge when the new version is available. |
eastlondoner
force-pushed
the
cluster-internal-ssl
branch
from
a4aece5
to
93c7106
Compare
eastlondoner
changed the title
|
note - needs verification against 4.1.2, or otherwise a helm version bump to 4.1.3 where it should work. @moxious to confirm |
No description provided.