Thanks a million Sushil finally was able to get it up and running(With
SSL). You just made my day, even though it's night time now :).
After the tweaks you suggested, it worked all fine.
Thanks again,
Atul
On Mon, Jul 27, 2020 at 11:49 PM Atul Wankhade
wrote:
> That's awesome, sure will take a
That's awesome, sure will take a look.
Thanks,
Atul
On Mon, Jul 27, 2020, 10:52 PM Sushil Kumar wrote:
> Hello Atul
>
> You can have a look at the chart at https://github.com/sushilkm/nifi-chart
> repository.
> I used this chart to generate and use self-signed certificates, and deploy
> it
Hello Atul
You can have a look at the chart at https://github.com/sushilkm/nifi-chart
repository.
I used this chart to generate and use self-signed certificates, and deploy
it over azure.
Couple of things to note before you use it:
storageclass -> you might need to change the value of
Hi Sushil,
Would you be kind enough to share the Helm chart unless it's confidential?
I really want to make this setup work. As said above I am generating the
certs in the init container, but I am not sure where they are getting
stored, when I am redirecting to a volume mount I am getting below
Hello Atul
I wrote the chart myself.
Cert generation pattern was similar to what you are trying.
I ran the server as a separate container, and generated client certs in
init-container.
Thanks
Sushil
On Sun, Jul 26, 2020, 9:46 AM Atul Wankhade
wrote:
> Hi Sushil,
>
> I am using Cetic helm
Hi Sushil,
I am using Cetic helm chart only. May I know which did you use? Where did
you generate the certs?
Thanks,
Atul
On Sat, Jul 25, 2020 at 2:00 AM Sushil Kumar wrote:
> Hello Atul
>
> I have recently tried using self signed certificates generated using nifi
> toolkit while using helm
Hello Atul
I have recently tried using self signed certificates generated using nifi
toolkit while using helm chart.
cetic helm chart is not written completely to accomplish this,
I may be able to help if you can share your helm chart.
However, as of now the error is in your values.yaml file.
I don't use our know much about helm, but that error suggests you've got
something wrong on line 202 of your yaml, so what's on that line (or the
lines immediately before/after)?
Notice you're using nifi 1.11.1, might be worth considering 1.11.4 if you
can to take advantage of several high
Chris I am trying what you have suggested, while passing the init container
params in values.yaml getting below error, can you please help to get
around this issue.
*Error: cannot load values.yaml: error converting YAML to JSON: yaml: line
202: did not find expected ',' or '}'*
I am adding below
Hi Andy,
Sorry for the confusion, Nifi is running inside a container on the
node(Image has java prebuilt). It seems I need to tweak the image to
generate the certs inside the container. I have done the same setup(worked
fine) On Azure where I used to generate the certs on VM itself for Node
Chris has a lot of good suggestions there. NiFi can accept certificates from
any provider as long as they meet certain requirements (EKU, SAN, no wildcard,
etc.). The toolkit was designed to make the process easier for people who could
not obtain their certificates elsewhere.
Maybe I am
My suggestion would be to run the apache/nifi-toolkit image as another Pod
within your k8s namespace and have it running as a TLS Server[1]. You'll
probably need to do that separately from your Helm chart (I'm not familiar
with Helm or this chart).
Then connect to that from your NiFi instances as
Thanks a lot Andy for your reply, it definitely helped pinpointing what is
going wrong. I tried simulating the same with the docker image from Apache
and generating the keystore/truststore files on the Docker host. For one
node NiFi it worked fine. The problem comes when I am trying the same on
Atul,
I am not a Kubernetes/ingress expert, but that error is indicating that you
specified NiFi should be secure (i.e. use TLS/HTTPS) and yet there is no
keystore or truststore provided to the application, so it fails to start. NiFi
differs from some other applications in that you cannot
Hi All,
I am trying to install NiFi with SSL on Kubernetes using Helm(cetic/nifi),
Below is my values.yaml. I keep getting an error on NiFi containers as - Am
I missing something?
*Caused by: org.springframework.beans.factory.BeanCreationException: Error
creating bean with name
15 matches
Mail list logo
