You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
commit-message: 'chore: update kube-stack-version and helm-version'
64
+
title: 'chore: update kube-stack-version and helm-version'
65
65
body: |
66
-
This PR automatically updates the `kube-stack-version` in `docset.yml` based on the latest version from the elastic-agent repository.
66
+
This PR automatically updates the `kube-stack-version` and `helm-version` in `docset.yml` based on the latest versions from the Kibana and Elastic Agent repositories.
67
67
68
68
**Changes:**
69
-
- Updated `kube-stack-version` to the latest value from elastic-agent repository
69
+
- Updated `kube-stack-version` to the latest value from the Kibana repository
70
+
- Updated `helm-version` to the latest value from the Elastic Agent repository
70
71
71
72
**Generated by:** [Update Kube Stack Version workflow](https://github.com/${{ github.repository }}/actions/workflows/update-kube-stack-version.yml)
72
73
73
74
This is an automated update. Please review the changes before merging.
74
75
branch: update-kube-stack-version
75
76
delete-branch: true
77
+
team-reviewers: |
78
+
ingest-docs
76
79
labels: |
77
80
automated
78
81
chore
@@ -91,7 +94,7 @@ jobs:
91
94
git diff HEAD -- docset.yml >> $GITHUB_STEP_SUMMARY
92
95
echo '```' >> $GITHUB_STEP_SUMMARY
93
96
else
94
-
echo "ℹ️ **No changes needed** - kube-stack-version is already up to date" >> $GITHUB_STEP_SUMMARY
97
+
echo "ℹ️ **No changes needed** - kube-stack-version and helm-version are already up to date" >> $GITHUB_STEP_SUMMARY
95
98
fi
96
99
97
100
- name: Summary
@@ -102,5 +105,5 @@ jobs:
102
105
if [ "${{ steps.check-changes.outputs.has_changes }}" == "true" ]; then
Use AutoOps in your {{ech}}, ECE, ECK, or self-managed deployments.
3
-
4
-
AutoOps is a monitoring tool that simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
AutoOps is a monitoring tool that simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. Learn more about [](/deploy-manage/monitor/autoops.md).
This path is not supported. Currently, we only support using Cloud Connect to connect ECE, ECK, and self-managed clusters to AutoOps.
2
2
3
-
For {{ech}} clusters, AutoOps is set up and enabled automatically in all supported [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md), and can be [accessed](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md#ec-autoops-how-to-access) from the deployment overview page.
3
+
For {{ech}} deployments, AutoOps is set up and enabled automatically in all supported [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md), and can be [accessed](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) from the deployment overview page.
Copy file name to clipboardExpand all lines: deploy-manage/api-keys/elastic-cloud-api-keys.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,9 +34,11 @@ These keys provides access to the API that enables you to manage your deployment
34
34
35
35
::::{note}
36
36
When an API key is nearing expiration, Elastic sends an email to the creator of the API key and each of the operational contacts. When you use an API key to authenticate, the API response header `X-Elastic-Api-Key-Expiration` indicates the key’s expiration date. You can log this value to detect API keys that are nearing expiration.
37
+
38
+
Once an API key expires, it will automatically be removed from the API Keys tab.
37
39
::::
38
40
39
-
5. Click **Create API key**, copy the generated API key, and store it in a safe place. You can also download the key as a CSV file.
41
+
6. Click **Create API key**, copy the generated API key, and store it in a safe place. You can also download the key as a CSV file.
40
42
41
43
The API key needs to be supplied in the `Authorization` header of a request, in the following format:
@@ -77,11 +77,11 @@ For the `role_descriptors` object schema, check out the [`/_security/api_key` en
77
77
78
78
## Update an API key [api-keys-update-an-api-key]
79
79
80
-
In **{{api-keys-app}}**, click on the name of the key. You can update only **Restrict privileges** and **Include metadata**.
80
+
In **API keys**, click on the name of the key. You can update only **Restrict privileges** and **Include metadata**.
81
81
82
82
83
83
## View and delete API keys [api-keys-view-and-delete-api-keys]
84
84
85
-
The **{{api-keys-app}}** app lists your API keys, including the name, date created, and status. When API keys expire, the status changes from `Active` to `Expired`.
85
+
The **API keys** app lists your API keys, including the name, date created, and status. When API keys expire, the status changes from `Active` to `Expired`.
Copy file name to clipboardExpand all lines: deploy-manage/autoscaling/autoscaling-deciders.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,7 @@ The estimation of expected additional data is based on past indexing that occurr
68
68
: (Optional, [time value](elasticsearch://reference/elasticsearch/rest-apis/api-conventions.md#time-units)) The window of time to use for forecasting. Defaults to 30 minutes.
This example puts an autoscaling policy named `my_autoscaling_policy`, overriding the proactive decider’s `forecast_window` to be 10 minutes.
74
74
@@ -143,7 +143,7 @@ Both `num_anomaly_jobs_in_queue` and `num_analytics_jobs_in_queue` are designed
143
143
: (Optional, [time value](elasticsearch://reference/elasticsearch/rest-apis/api-conventions.md#time-units)) Specifies the time to delay before scaling down. Defaults to 1 hour. If a scale down is possible for the entire time window, then a scale down is requested. If the cluster requires a scale up during the window, the window is reset.
0 commit comments