Flux maintenance notification (#5149)

* Flux notification

* updated flux messaging
pull/5151/head
Scott Anderson 2023-09-21 08:00:09 -06:00 committed by GitHub
parent f0e6830ec5
commit d59534b830
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 25 additions and 0 deletions

View File

@ -143,6 +143,7 @@
margin: 0; margin: 0;
padding: 0; padding: 0;
opacity: 0; opacity: 0;
pointer-events: none;
} }
.show::before {content: "Show more"} .show::before {content: "Show more"}
} }

View File

@ -27,6 +27,30 @@
[Learn more](https://www.influxdata.com/blog/announcing-influxdb-clustered/) [Learn more](https://www.influxdata.com/blog/announcing-influxdb-clustered/)
[Contact InfluxData Sales](https://www.influxdata.com/contact-sales-influxdb-clustered) [Contact InfluxData Sales](https://www.influxdata.com/contact-sales-influxdb-clustered)
- id: future-of-flux
level: warn
scope:
- /flux/v0
- /influxdb/v1
- /influxdb/v2
- /influxdb/cloud/
title: The future of Flux
slug: |
Flux is going into maintenance mode. You can continue using it as you
currently are without any changes to your code.
message: |
Flux is going into maintenance mode and will not be supported in InfluxDB 3.0.
This was a decision based on the broad demand for SQL and the continued growth
and adoption of InfluxQL. We are continuing to support Flux for users in 1.x
and 2.x so you can continue using it with no changes to your code.
If you are interested in transitioning to InfluxDB 3.0 and want to
future-proof your code, we suggest using InfluxQL.
For information about the future of Flux, see the following:
- [The plan for InfluxDB 3.0 Open Source](https://influxdata.com/blog/the-plan-for-influxdb-3-0-open-source)
- [InfluxDB 3.0 benchmarks](https://influxdata.com/blog/influxdb-3-0-is-2.5x-45x-faster-compared-to-influxdb-open-source/)
- id: serverless-wip - id: serverless-wip
level: warn level: warn
scope: scope: