Helm install returns errors for post secrets

[tstevens]

Describe the bug For one of my clusters, I'm unable install the basic chart without an error from helm. Even using the example from the README shows the issue. From some minor research it seems like the NiFi registry chart is trying to deploy a default DB as a base64 encoded secret which might be too large. I'm not sure this is exactly a bug, but depending on the Kubernetes cluster configuration/version it seems sometimes it will deploy without issue as happens on my local cluster or returns an error as happens with a Rancher based cluster I'm attempting to deploy to.

Version of Helm and Kubernetes: Helm:

version.BuildInfo{Version:"v3.4.1", GitCommit:"c4e74854886b2efe3321e185578e6db9be0a6e29", GitTreeState:"dirty", GoVersion:"go1.15.4"}

Kube:

Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:50:19Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.5", GitCommit:"e0fccafd69541e3750d460ba0f9743b90336f24f", GitTreeState:"clean", BuildDate:"2020-04-16T11:35:47Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

What happened: Helm install returns an error

What you expected to happen: Helm installs the chart without error

How to reproduce it (as minimally and precisely as possible): Just attempting a basic helm install from the README is enough to trigger the issue.

helm install my-release cetic/nifi -n test --create-namespace

Error: the server responded with the status code 413 but did not return more information (post secrets)

Anything else we need to know: I have been able to get this to install without error into the Docker Kubernetes cluster on Mac.

[tstevens]

I've been able to verify older versions before #58 was merged install without issues, I've specifically checked 0.4.1 & 0.4.4. It seems like this might be the line causing issues, secret.yaml#L10.

Also, failed to note this above. While the README install example fails, my general use case is having NiFi as a chart dependency which also causes the same failure against the Rancher cluster. I have noticed that if I helm install --dry-run on my chart with the helm-nifi dependency and check the output, the resulting yaml is much larger once I use 0.5.0 or greater. Checking the output locally, 0.4.4 results in 110 KB vs 0.5.0 at 1.2 MB.

[banzo]

adding @daniel-yavorovich to the conversation in case he can provide some insights.

[jarrettprosser]

I came across this issue also. When deploying the helm chart with the default configuration and the nifi-registry enabled, deployment of the secret failed with the error Secret "nifi-registry-config" is invalid: metadata.annotations: Too long: must have at most 262144 characters. As a workaround, I've forked my own nifi registry chart and removed the sample database, which now deploys with no problems.