Conversation
da4b929 to
d1caabf
Compare
Signed-off-by: PERES-Richard <richard.peres@orange.com> Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: PERES-Richard <richard.peres@orange.com> Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
4f38f9b to
93346b1
Compare
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
|
Okay, I've tested all the implementation on GKE and it's working as expected ! Despite that, the PR is ready for review :) |
…ke pkiBackend management stateless Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com> Signed-off-by: PERES-Richard <richard.peres@orange.com>
f018704 to
4146938
Compare
Signed-off-by: PERES-Richard <richard.peres@orange.com>
4146938 to
885ca28
Compare
Signed-off-by: Richard Peres <richard.peres@orange.com> Signed-off-by: PERES-Richard <richard.peres@orange.com>
63cfe7f to
76158cf
Compare
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
Signed-off-by: Richard Peres <richard.peres@orange.com>
|
|
What's in this PR?
A (Work In Progress) implementation of a custom, integrated, self signed and autonomous way to ensure TLS secured communication even without cert manager deployed. It basically reproduces the cert manager fundamental behavior by delivering self signed tls certs to all Nificlusters and NifiUsers upon specific event which required cert generation.
Why?
To be able to use Nifikop with TLS secured Nificluster without using cert-manager. This makes Nifikop it's own, self-signed CA and certs deliverer. Very useful in specific cluster environments where you cannot deploy cert manager.
Finally, this is also useful because it prevents current strong dependency among Nifikop and Cert Manager in order to deploy secure communication for Nificlusters & NifiUsers.
Downsides are that self manager it's incompatible with user provided certs & issuers. So its an alternative to the use of cert manager for 'auto generate' certs only. Also, it's a dummy implementation of certs management and it should be used only when you cannot use cert-manager.
Checklist
RoadMap