diff --git a/build/azure-devops/agents-ci-scraper.yml b/build/azure-devops/agents-ci-scraper.yml index b814e78f1..b46e0db7c 100644 --- a/build/azure-devops/agents-ci-scraper.yml +++ b/build/azure-devops/agents-ci-scraper.yml @@ -272,22 +272,6 @@ stages: - template: templates/docker/push-image.yml parameters: imageName: '$(Image.TaggedName)' -- stage: Helm2 - displayName: Helm Chart (2.x) - dependsOn: Docker - jobs: - - job: Helm2_x - displayName: Helm 2.x - Lint - condition: succeeded() - variables: - Helm.Version: '2.9.1' - pool: - vmImage: ubuntu-16.04 - steps: - - template: templates/helm/lint-chart.yml - parameters: - helmVersion: '$(Helm.Version)' - chartName: '$(Chart.Scraper.Name)' - template: templates/stages/helm-chart-verification.yml parameters: chartName: '$(Helm.Chart.Name)' diff --git a/changelog/content/deprecated/helm-2.0.md b/changelog/content/deprecated/helm-2.0.md new file mode 100644 index 000000000..4aef1f09f --- /dev/null +++ b/changelog/content/deprecated/helm-2.0.md @@ -0,0 +1,28 @@ +--- +title: +subtitle: created on {{ now.Format "2020-11-23" }} +date: 2020-11-23T12:00:00+01:00 +removal_date: 2020-11-23 +weight: +version: +--- + +#### Helm 2.0 + +###### Deprecated as of v1.6 and will be removed in v2.0 + +Promitor provides Helm charts to simplify deployments on a Kubernetes cluster. + +In November 2019, Helm 3 was announced which marked the end of Helm 2 which would be phased out in a year and no longer + supported. Learn more about it in the official [Helm deprecation timeline](https://helm.sh/blog/helm-v2-deprecation-timeline/). + +Because of this deprecation, Promitor will no longer support Helm 2.0 deployments out-of-the-box. They might still be + working but won't be our focus for versions as of Promitor 2.0. + +**Announcement:** [GitHub Issue](https://github.com/tomkerkhove/promitor/issues/1371) + +**Impact:** Migration is required - Helm 2.0 deployments might still be working but is no longer supported. + +**Alternative:** Use Helm 3.0 by following [Helm migration guide](https://helm.sh/docs/topics/v2_v3_migration/). + +**Discussion:** [GitHub Discussions](https://github.com/tomkerkhove/promitor/discussions/1375) diff --git a/changelog/content/deprecated/prometheus-legacy-configuration.md b/changelog/content/deprecated/prometheus-legacy-configuration.md index 8f81b2543..3732b3d54 100644 --- a/changelog/content/deprecated/prometheus-legacy-configuration.md +++ b/changelog/content/deprecated/prometheus-legacy-configuration.md @@ -23,8 +23,10 @@ Because of that we are removing support for the "legacy" Prometheus configuratio We've added support for Prometheus metric sink while maintaining the legacy approach until it's being removed. +**Announcement:** [GitHub Issue](https://github.com/tomkerkhove/promitor/issues/1032) + **Impact:** Migration is required - Prometheus legacy configuration will no longer be available. **Alternative:** Use our new [metric sink concept](https://promitor.io/configuration/v1.x/runtime#prometheus-scraping-endpoint). -**Discussion:** [GitHub Issue #1032](https://github.com/tomkerkhove/promitor/issues/1032) +**Discussion:** [GitHub Discussions](https://github.com/tomkerkhove/promitor/discussions/1372) diff --git a/changelog/content/deprecated/swagger-2.0.md b/changelog/content/deprecated/swagger-2.0.md index 03b7cad24..f3cb97f23 100644 --- a/changelog/content/deprecated/swagger-2.0.md +++ b/changelog/content/deprecated/swagger-2.0.md @@ -1,4 +1,5 @@ --- +title: subtitle: created on {{ now.Format "2020-01-07" }} date: 2018-09-02T20:46:47+02:00 removal_date: 2020-01-07 @@ -17,8 +18,10 @@ with 3.0 instead of 2.0. We've added support for OpenAPI 3.0 in Promitor v1.1 next to Swagger 2.0 so you can migrate to it before we remove 2.0 in Promitor v2.0. +**Announcement:** [GitHub Issue](https://github.com/tomkerkhove/promitor/issues/782) + **Impact:** Migration is required - API documentation will no longer be available. **Alternative:** Use API documentation provided in OpenAPI v3.0 format. -**Discussion:** [GitHub Issue #782](https://github.com/tomkerkhove/promitor/issues/782) +**Discussion:** [GitHub Discussions](https://github.com/tomkerkhove/promitor/discussions/1374) diff --git a/changelog/content/deprecated/swagger-ui-2.0.md b/changelog/content/deprecated/swagger-ui-2.0.md index 6ff0a3c65..6344671eb 100644 --- a/changelog/content/deprecated/swagger-ui-2.0.md +++ b/changelog/content/deprecated/swagger-ui-2.0.md @@ -18,8 +18,10 @@ with 3.0 instead of 2.0. We've added support for OpenAPI 3.0 in Promitor v1.1 next to Swagger 2.0 along with OpenAPI UI 3.0. +**Announcement:** [GitHub Issue](https://github.com/tomkerkhove/promitor/issues/781) + **Impact:** Migration is required - Swagger UI 2.0 will no longer be available. **Alternative:** Use OpenAPI UI 3.0. -**Discussion:** [GitHub Issue #781](https://github.com/tomkerkhove/promitor/issues/781) \ No newline at end of file +**Discussion:** [GitHub Discussions](https://github.com/tomkerkhove/promitor/discussions/1373) diff --git a/changelog/content/experimental/unreleased.md b/changelog/content/experimental/unreleased.md index 7fa3ab426..7e78c2cdd 100644 --- a/changelog/content/experimental/unreleased.md +++ b/changelog/content/experimental/unreleased.md @@ -42,6 +42,8 @@ version: | [FAQ](https://promitor.io/faq#why-does-my-multi-dimensional-metric-report-label-value-unknown-with-prometheus)). - {{% tag removed %}} Support for Prometheus legacy configuration ([deprecation notice](https://changelog.promitor.io/#prometheus-legacy-configuration) | [migration guide](https://promitor.io/walkthrough/migrate-from-1.x-to-2.x)) +- {{% tag removed %}} Support for Helm 2.0 ([deprecation notice](https://changelog.promitor.io/#helm-2-0) | + [Helm migration guide](https://helm.sh/docs/topics/v2_v3_migration/)) - {{% tag removed %}} Support for Swagger UI 2.0 ([deprecation notice](https://changelog.promitor.io/#swagger-ui-2-0) | [migration guide](https://promitor.io/walkthrough/migrate-from-1.x-to-2.x)) - {{% tag removed %}} Support for Swagger 2.0 ([deprecation notice](https://changelog.promitor.io/#swagger-2-0) | diff --git a/docs/faq.md b/docs/faq.md index 642e60f2f..98750e6be 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -5,24 +5,26 @@ title: Frequently asked questions (FAQs) Here are a list of questions you may have: -- [What Azure clouds are supported?](#what-azure-clouds-are-supported) -- [What operating systems are supported?](#what-operating-systems-are-supported) -- [Is scraping multiple subscriptions supported?](#is-scraping-multiple-subscriptions-supported) - [Are multi-dimensional metrics supported?](#are-multi-dimensional-metrics-supported) +- [Is scraping multiple subscriptions supported?](#is-scraping-multiple-subscriptions-supported) +- [What Azure clouds are supported?](#what-azure-clouds-are-supported) - [Why does Azure Blob & File Storage only report account-level information?](#why-does-azure-blob--file-storage-only-report-account-level-information) - [Why does my multi-dimensional metric report label value `unknown` with Prometheus?](#why-does-my-multi-dimensional-metric-report-label-value-unknown-with-prometheus) +- [What Helm version is supported?](#what-helm-version-is-supported) +- [What operating systems are supported?](#what-operating-systems-are-supported) -## What Azure clouds are supported? - -We support `Global` (default), `China`, `UsGov` & `Germany` Azure clouds. - -This can be configured in the metric configuration under `azureMetadata`. +## Are multi-dimensional metrics supported? -For more information see our ['Metric Configuration' page](/configuration/v1.x/metrics/#metrics). +Yes, every scraper supports scraping multi-dimensional metrics except for +Azure Storage queues. -## What operating systems are supported? +You can configure the dimension you are interested in via +`azureMetricConfiguration.dimension.Name`, for more information see +our ['Metric Configuration' page](/configuration/v1.x/metrics/#metrics). -We support running on both Linux & Windows platforms. +However, you can only use it with metrics in Azure Monitor that support this, +for a complete overview we recommend reading the +[official documentation](https://docs.microsoft.com/en-us/azure/azure-monitor/platform/metrics-supported). ## Is scraping multiple subscriptions supported? @@ -33,18 +35,13 @@ However, you can deploy multiple instances of Promitor that each scrape another We have it on [our backlog](https://github.com/tomkerkhove/promitor/issues/761) to see if there is enough demand for it, feel free to give a :+1:. If that is the case, we will reconsider this limitation. -## Are multi-dimensional metrics supported? +## What Azure clouds are supported? -Yes, every scraper supports scraping multi-dimensional metrics except for -Azure Storage queues. +We support `Global` (default), `China`, `UsGov` & `Germany` Azure clouds. -You can configure the dimension you are interested in via -`azureMetricConfiguration.dimension.Name`, for more information see -our ['Metric Configuration' page](/configuration/v1.x/metrics/#metrics). +This can be configured in the metric configuration under `azureMetadata`. -However, you can only use it with metrics in Azure Monitor that support this, -for a complete overview we recommend reading the -[official documentation](https://docs.microsoft.com/en-us/azure/azure-monitor/platform/metrics-supported). +For more information see our ['Metric Configuration' page](/configuration/v1.x/metrics/#metrics). ## Why does Azure Blob & File Storage only report account-level information? @@ -60,4 +57,20 @@ When Promitor is unable to find a metric for a multi-dimensional metric, it will You can read more about it in our [Prometheus sink documentation](/configuration/v2.x/runtime/scraper/#what-happens-when-metrics-are-unavailable-for-multi-dimensional-metrics). +## What Helm version is supported? + +Promitor supports deployments with **Helm v3.0** for all versions. + +Helm has [deprecated support for v2.0](https://helm.sh/blog/helm-v2-deprecation-timeline/) and is out of support. + Because of that, Promitor supported to remove support for Helm 2.0 as of Promitor 2.0. + +However, while we don't support it out-of-the-box it is possible that it is still compatible with Helm 2.0 but we do + not provide support for it. + +Join the discussion on our Helm v2.0 support deprecation on [GitHub Discussions](https://github.com/tomkerkhove/promitor/discussions/1375). + +## What operating systems are supported? + +We support running on both Linux & Windows platforms. + [← back](/)