[KARAF-7145] Add kube namespace config option#86
Conversation
|
Tested OK (with some additions): I added a kube-client autoconfiguration facility and made this work (avoiding some NPE traps). Also added some docs which I would have found useful while putting the Kubernetes discovery mechanism in use. Keep me posted if you find this interesting. |
|
FYI, there is a complete refactoring of Cellar ongoing (Cellar 3.x). |
You might be using these version references (3.x, 2.x) internally. The current patch(es) were made against the main branch of the cellar repo, which is supposed to build 4.2.2-SNAPSHOT. Will these refactorings bump the version to 5.x.x? Or to 4.3.x? @fpapon I will squash the commits and rebase on the current main |
Add new kubernetes.autoConfig option, leveraging fabric8 kubernetes client Config.autoConfigure() function. Fix NPE during node startup if kubernetes discovery provides pod IPs before hazelcast is up. Fix NPE when handling empty TLS options. Document use of kubernetes.autoConfig and kubernetes.namespace. Add sample on using kubernetes service accounts automatically and manually
CMoH
force-pushed
the
karaf-7145_kube-namespace-setting
branch
from
f902d84 to
b5ad48d
Compare
|
Sorry I wasn't clear: I will create cellar 4.x branch. Mail will become cellar 5.x and will welcome the big refactoring (locally on my machine for now). |
|
Rebased. Seems all tests pass |
|
@CMoH thanks ! Let me do a new pass. |
3 participants
I still have to test this, but I will certainly have to, because I need to put this setting to use.
From the code it seems this is all that's needed to configure the kubernetes client to work within the confines of a single namespace. Any notes/hints are welcome.