Skip to content
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

Upgrade to Node 14.x #83154

Closed
mshustov opened this issue Nov 11, 2020 · 4 comments
Closed

Upgrade to Node 14.x #83154

mshustov opened this issue Nov 11, 2020 · 4 comments
Labels
discuss Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Operations Team label for Operations Team

Comments

@mshustov
Copy link
Contributor

Kibana should use nodejs v14 for v7.last release. According to our policy, we support the v7.last version until v9.0 is released (in ~2-2.5 years from now). Which means we cannot release v7.last with nodejs12 with the end of support on 30.04.2022
The same problem exists for v8.0 that's going to be released less than one year before nodejs v12 end of support.

Not sure which team owns this responsibility considering all the latest changes: @elastic/kibana-operations or @elastic/kibana-platform, considering that's a runtime environment and likely will require some tweaks in the platform & plugin code.

@mshustov mshustov added discuss Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Operations Team label for Operations Team labels Nov 11, 2020
@kobelb
Copy link
Contributor

kobelb commented Nov 11, 2020

Historically, we've had the operations team perform node upgrades. However, given their recent focus on the build, CI, and developer tooling, it feels a bit off. I was hoping that the files that had to be changed to upgrade to Node 12 would be revealing, but it looks like small changes were required to a bunch of things. Do the people that have historically done these upgrades have an opinion?

@tylersmalley
Copy link
Contributor

I don't have a preference for which team ultimately owns it. We're currently tracking that as a blocker for 8.0 here: #54039

@spalger
Copy link
Contributor

spalger commented Nov 12, 2020

I personally like the volunteer model we've followed so far. Operations and Platform usually have a decent amount of involvement, though I personally think of it as an operations concern, though it's usually a very cross-team effort for major upgrades.

@mshustov
Copy link
Contributor Author

mshustov commented Nov 16, 2020

closed in favour of #54039

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Operations Team label for Operations Team
Projects
None yet
Development

No branches or pull requests

4 participants