-
Notifications
You must be signed in to change notification settings - Fork 228
Support Enable/Disable NiFi Zookeeper client Zookeeper Ensemble Tracker #294
Support Enable/Disable NiFi Zookeeper client Zookeeper Ensemble Tracker #294
Conversation
This is bumping NiFi to 1.20 also, nice, thanks! Unfortunately one of the tests fails: https://github.com/cetic/helm-nifi/blob/253ad43b273075bf91165f320bac3794a2446d4f/.github/workflows/test-site-to-site.yml
|
Signed-off-by: Tan Luu <[email protected]>
Signed-off-by: Tan Luu <[email protected]>
* Fix s2s test Signed-off-by: Tan Luu <[email protected]>
thank you, can you please update the PR title and description to reflect the change in NiFi version? This will help to autogenerate the release notes. Also I am curious what is the difference between the cert-manager.io and jetstack versions for cert-manager. |
Hi @banzo , |
When you point a web browser to https://github.com/jetstack/cert-manager it automatically redirects to https://github.com/cert-manager/cert-manager so I would recommend reverting to the cert-manager.io URL, as it seems to be the long-term supported reference to that project. |
cmctl -n alpha renew nifi-0 | ||
kubectl -n alpha rollout restart statefulset/nifi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This defeats the purpose of the test, which was to confirm that NiFi is automatically detecting the certificate has changed and restarting the TLS modules. If we want to disable this test because NiFi is broken, then I would recommend commenting it out with a comment rather than forcing a restart.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a TODO to remove this block of code when NIFI issue is fixed
Signed-off-by: Tan Luu <[email protected]>
* Add session affinity FAQ --------- Co-authored-by: Chengjun Fu <[email protected]>
…etic#301) Signed-off-by: Michael Dent <[email protected]> Co-authored-by: Michael Dent <[email protected]>
* Update nifi.properties - Add values - nifi.security.user.oidc.preferred.jwsalgorithm={{.Values.auth.oidc.preferredJwsalgorithm}} * Update values.yaml - Add auth.oidc.preferredJwsalgorithm value * Update README.md - Add info about nifi.security.user.oidc.preferred.jwsalgorithm
Signed-off-by: joseph.ybh <[email protected]> Co-authored-by: joseph.ybh <[email protected]>
Signed-off-by: Tan Luu <[email protected]>
Signed-off-by: Tan Luu <[email protected]>
* Fix s2s test Signed-off-by: Tan Luu <[email protected]>
Signed-off-by: Tan Luu <[email protected]>
…m:nathluu/helm-nifi into nathluu/zkclient-ensemble-tracker-disable
What this PR does / why we need it:
From NiFi 1.20.0 it supports configuration to enable/disable Zookeeper(zk) client zk Ensemble Tracker as of NIFI-10481.
With zk ensemble tracker enabled (default by NiFi), nifi zk client resolves the zk connection string to IP addresses then when all zk server pods get restarted and come up with a different IP, NiFi pods cannot reconnect to zk.
Which issue this PR fixes
(optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged)Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]