[stable/kibana] Migration Tracker

[compleatang]

In collaboration with the team at elastic, @monotek and I the maintainers of the kibana chart have decided to put the chart into a "pre-depreaction" status. Given that the elasticsearch chart is moving over it makes sense to move Kibana over too.

Old Chart: https://github.com/helm/charts/tree/master/stable/kibana
New Chart: https://github.com/elastic/helm-charts/tree/master/kibana

This issue should operate as the central tracking issue for work that has been and will be accomplished in this migration path.

General

• Add a pre-migration notice to stable/kibana's README
• Close off all issues that deal with v7.X upgrades and refer them to this issue and/or the elastic charts for their improvements to the stable/kibana chart
• Decide a deadline for "actually" deprecating the chart and follow the procedures here
• Finalize whether elastic/kibana needs a migration guide similar to elastics ... my early view is that there is no need due to the relatively stateless positioning of stable/kibana

Specific Functionality

The below functionality of the stable/kibana chart should ideally be migrated to elastic/kibana:

• PVCs for plugins (whole file)
• Service Account flexibility (whole file rather than simple invocation
• Services:
  • Labels
  • loadBalancerSourceRanges
  • clusterIP (ability to customize)
  • loadBalancerIP
  • customizable selectors
  • non-cluster-IP service types
  • authProxyEnabled functionality
• Ingress:
  • allow path element in ingress values from (feature(kibana): allow path element in ingress values #9028)
• Dashboard import feature
• Deployments
  • deployment annotations
  • revisionHistoryLimit
  • podAnnotations
  • podLabels
  • init containers work
  • pullPolicy
  • commandline.args
  • envFromSecrets
  • authProxyEnabled
  • probes flexibility (timing mostly)
  • extraVolumeMounts
  • extraContainers
  • extraConfigMapMounts
  • extraVolumes
  • dashboardImport.enabled
  • plugins.enabled

Test functionality

It's unclear to me at this time what we should do with the tests because it appears that the helm-elastic repo has it's own python based test runner.

cc @monotek @Crazybus @jethr0null if I missed anything.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[compleatang]

not stale. still actionable.

[monotek]

pr to add dashboard import: elastic/helm-charts#244

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[monotek]

Not stale.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[monotek]

Not stale.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[monotek]

@compleatang
Imho we can deprecate the chart.

Im pretty sure we'll see PRs pretty soon, if some of the features are needed in the official chart.
To be honest, i don't even use Kibana at the moment, as we switched to Stackdriver at work and Im i also thinking about to try out Loki for a private project, so i lost a bit of interest in EFK stack.

[compleatang]

actually, same, we've moved to stackdriver as well.

[monotek]

I've added a pr to deprecate the chart: #23844

[compleatang]

👍