-
Notifications
You must be signed in to change notification settings - Fork 8.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
Remove kibana.index
, xpack.reporting.index
, xpack.task_manager.index
settings
#101964
Comments
Pinging @elastic/kibana-core (Team:Core) |
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
Pinging @elastic/kibana-app-services (Team:AppServices) |
/cc @cachedout |
I've created #102076 to remove |
We've run into some difficulties during our exploration of the workaround previously recommended by the Kibana folks to use either CCR or CCS. Our next step will be to explore ways that we can spin up ES instances for each developer in Observability which comes complete with a sample data set large enough for them to do their development work. |
xpack.index
, xpack.reporting.index
, xpack.task_manager.index
settingskibana.index
, xpack.reporting.index
, xpack.task_manager.index
settings
Just a friendly reminder that this is something we need to do for 8.0; however, it's still blocked by Observability's use for their dev environments. Given the fact that we're getting close to the 8.0 FF, it might be wise to get a PR together for this so it can be merged as soon as Observability no longer required it. |
ack: this is something that's on our radar & we already have in our queue for 2-3 weeks from now. if the observability team isn't moved off it in the next week or two, we will plan to move forward on a draft PR. |
@kobelb and @lukeelmers We (Observability) have been focusing on this and we're making good progress. We've finished most of the moving pieces and just have a small CLI client and some docs left to write. Could you check back with us at the end of next week (Sept 17) for a status? |
Nice to hear that!
Ack. Should we ping you on https://github.com/elastic/observability-test-environments/issues/915 or on this issue? |
@pgayvallet elastic/observability-test-environments#915 is our main tracking issue so that would be the best place. Thanks! |
@elastic/kibana-reporting-services do you have a dedicated issue for the removal of |
kibana.index
, xpack.reporting.index
, xpack.task_manager.index
settingsxpack.index
, xpack.reporting.index
, xpack.task_manager.index
settings
xpack.index
, xpack.reporting.index
, xpack.task_manager.index
settingskibana.index
, xpack.reporting.index
, xpack.task_manager.index
settings
@pgayvallet From the Slack conversion with @tsullivan
|
PR: #113803 |
As discussed in #82020, we will be removing the following settings in 8.0:
kibana.index
- [8.0] removekibana.index
config property #112773xpack.reporting.index
- [Reporting] Breaking: Remove setting for Reporting index #113803xpack.task_manager.index
- [8.0 only] Removexpack.task_manager.index
setting #102076These settings have already been deprecated in 7.x; however, they have not been removed from
master
.The Observability team currently takes advantage of these settings to allow their developers to use a multi-tenant Cloud environment. They are actively testing a few approaches to do so, but haven't implemented one yet. As a result, we should delay removing these settings until they have a path forward.
Blocked by https://github.com/elastic/observability-test-environments/issues/915
The text was updated successfully, but these errors were encountered: