Comments (14)
You can see my manifest here - Orange-OpenSource/nifikop#139 , as I said I only added nifi.sensitive.props.key
from nifikop.
Oh, yeah, I'm not using cert-manager
from nifikop.
I was able to get it working. The nifi logs inform you what needs to be added to get it to work.
Can you clarify specifically what isn't working?
from nifikop.
nifi.sensitive.props.key
would you mind shring the manifest for the cluster with your settings? i suspect mi issues comes from using the certificate manager... thanks
from nifikop.
nifi.sensitive.props.key
would you mind shring the manifest for the cluster with your settings? i suspect mi issues comes from using the certificate manager... thanks
I did just recently discover #153
But otherwise, it should work just fine. I've cert-manager enabled (deployed version v1.5.4) in my setup without issues.
Are there errors in the nifikop logs or the nifi-app logs?
from nifikop.
We are working on the integration with NiFi 1.14 and NiFi 1.15, it seems after some tests that everything works perfectly with these new versions (if you add property
nifi.sensitive.props.key
in thenifi.properties
) in case you are already on a secured cluster.For unsecure clusters, I don't touch all the things that it involves, but if there isn't a detailed clear process somewhere, I assume that the operator won't support the upgrade.
Thanks @erdrix - I will try ASAP and report how it goes
from nifikop.
@erdrix my nifi setup include cert manger version 1.2 , after adding the key "nifi.sensitive.props.key" the pods keep restarting in a loop and i cant debug it.
do you test it with cert manger enabled ? any ideas ? thanks
from nifikop.
I got it working too, the only change I had to make was to explicitly provide nifi.sensitive.props.key in overrideConfigs. It is working with 1.15.0 too
from nifikop.
nifi.sensitive.props.key
would you mind shring the manifest for the cluster with your settings? i suspect mi issues comes from using the certificate manager... thanks
I did just recently discover #153
But otherwise, it should work just fine. I've cert-manager enabled (deployed version v1.5.4) in my setup without issues.
Are there errors in the nifikop logs or the nifi-app logs?
It is hard to debug since Nifikop fails to start the pods and kills them before i can debug... and all i did was change the version on my working setup
from nifikop.
We are working on the integration with NiFi 1.14 and NiFi 1.15, it seems after some tests that everything works perfectly with these new versions (if you add property nifi.sensitive.props.key
in the nifi.properties
) in case you are already on a secured cluster.
For unsecure clusters, I don't touch all the things that it involves, but if there isn't a detailed clear process somewhere, I assume that the operator won't support the upgrade.
from nifikop.
For the nifi.sensitive.props.key
we are balanced between letting people configure it using the nifiProperties. overrideSecretConfig
or explicitly set a secretconfigreference for this nifi property.
We have not tested the version 1.14
and 1.15
so we don't explicitly support these two version (We have some rework to replace the unsecured mode which has changed and require new configurations : username and password).
from nifikop.
I got it working too, the only change I had to make was to explicitly provide nifi.sensitive.props.key in overrideConfigs. It is working with 1.15.0 too
I just tested with the simplecluster.yaml just changing the versions and it doesn't work for me. Thanks for all your support :)
from nifikop.
deleting the certs related to nifi forced the cert manger to create new certs and now its working
from nifikop.
We are working on the integration with NiFi 1.14 and NiFi 1.15, it seems after some tests that everything works perfectly with these new versions (if you add property
nifi.sensitive.props.key
in thenifi.properties
) in case you are already on a secured cluster.
For unsecure clusters, I don't touch all the things that it involves, but if there isn't a detailed clear process somewhere, I assume that the operator won't support the upgrade.Thanks @erdrix - I will try ASAP and report how it goes
After some additional test we faced to some issues during the upgrade, the following actions should works to migrate from 1.12.X or 1.13.X to 1.14+ :
- Edit your
NiFiCluster
resource by adding an init container :
...
spec
...
initContainers:
...
- command:
- sh
- -c
- '/opt/nifi/nifi-current/bin/nifi.sh set-sensitive-properties-key <your encryption password>'
image: apache/nifi:1.14.0
imagePullPolicy: IfNotPresent
name: upgrade-nifi
volumeMounts:
- mountPath: /opt/nifi/data
name: data
- mountPath: /opt/nifi/nifi-current/conf
name: conf
...
-
Add your sensitive key in your
nifi.properties
(using one of the three possibility, it is highly recommended to use a secret) :nifi.sensitive.props.key=<your encryption password>
. -
Force the deletion of all your NiFi node's pods, in a way that they will start in the same time.
-
Once all the pods of your cluster are up, edit once again your NiFiCluster resource, by removing the added
initContainer
and upgrading your NiFi version :
spec
...
clusterImage: apache/nifi:1.15.1
...
And your cluster should be running :)
from nifikop.
Related Issues (20)
- nifikop 1.6.0 duplicates flow on canvas (deploys two instead of one) HOT 9
- Allow NiFi properties to be configured via environment variables
- Refactor NifiCluster state management CRD Configuration HOT 2
- Introduce `NifiCluster` v2alpha1
- Update NiFi configuration in nifikop for NiFi 2.0.0 HOT 6
- Migrate nifikop to KubeBuilder go/v4 from go/v3
- Not able to spin nificluster using helm chart not Basic nificluster configuration Giving nil pointer error HOT 1
- Nifikop pod is crashing when sample cluster yaml file is applied . HOT 3
- Nifikop sets Group names to namespace-name, which breaks OIDC group claim-based authorization
- Remove Bootstrap notifications for nifikop 2.0.0
- LDAPS - Active Directory Authentication HOT 1
- The `NifiUser` DNSNames of the cluster nodes aren't update if the `webProxyHosts` is.
- Common CA with external cluster HOT 4
- Add a new resource to deploy extensions (custom processor) into nifi HOT 10
- `nifi-cluster` helm chart template wraps two lines together
- Add support for configuring `Service` traffic policies
- When using read only authorizerConfig it is not used when adding new nodes HOT 1
- Ability to set Health check paths within one service HOT 2
- How to correctly configure single user configuration with https (via cert-manager)? HOT 2
- write access on a process-group always creates write access on NifiFlow process group (top level) HOT 8
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 nifikop.