-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bitnami/kibana] importing ndjson as configmap #6159
Comments
Hi, Could you provide a minimal ndjson example that triggers the error? We would like to reproduce the issue in our side. |
Unfortunately I'm not really sure what the "minimal" ndjson file is. The file that I get by going through the reproduce steps is pretty huge and it's just for the index. I'll try to regenerate later today. |
My export.ndjson. Probably has a lot of fields due to my kubernetes filter
|
Hi, I was able to reproduce the issue and I think the problem is with our current status check logic. Note that we are close to perform a major change in the chart that includes a bash-based Kibana. I believe the issue should not be there once it is updated. This should happen soon. |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Now we have a bash-based Kibana solution. Could you check if the issue is still there? |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Sorry I haven't been able to get around to this. Is there new documentation for the new solution? |
Hi, You should be able to use the same parameters. Did it fail this time? |
@javsalgar Success!!! This resulted in a templates/kibana.yaml file which looks like the following:
This is after I delete the managedFields which will apparently not show up starting at 1.21 (kubernetes/kubernetes#90066) as well as the creationTimestamp, namespace, resourceVersion, selfLink, and uid fields. |
Thanks for letting us know!! |
Which chart:
kibana: 7.2.5
Describe the bug
Kibana crashes when importing kibana exported ndjson file as configmap
To Reproduce
Steps to reproduce the behavior:
name: kibana
.Expected behavior
Kibana successfully imports existing config and starts
Version of Helm and Kubernetes:
helm version
:kubectl version
:The text was updated successfully, but these errors were encountered: