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
Copy file name to clipboardExpand all lines: deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -102,6 +102,10 @@ Select one of the following methods to install {{agent}}:
102
102
* **Windows**
103
103
-->
104
104
105
+
:::{note}
106
+
macOS is not a supported platform for installing {{agent}} to connect to AutoOps in a self-managed production environment. However, you can use macOS to [connect your local development cluster to AutoOps](/deploy-manage/monitor/autoops/cc-connect-local-dev-to-autoops.md).
107
+
:::
108
+
105
109
:::{important}
106
110
Using AutoOps for your ECE, ECK, and self-managed clusters requires a new, dedicated {{agent}}. You must install an agent even if you already have an existing one for other purposes.
@@ -38,8 +39,7 @@ Whether you are using AutoOps in your [{{ech}} deployment](/deploy-manage/monito
38
39
39
40
**Setting up AutoOps for self-managed clusters**
40
41
*[Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps?](#cc-autoops-ech)
41
-
*[Can I use AutoOps for my clusters if my environment is air-gapped?](#autoops-air-gapped)
42
-
*[Can I use macOS to install {{agent}} for this feature?](#macos-install)
42
+
*[Can I use macOS to set up AutoOps for my self-managed clusters?](#macos-install)
43
43
*[Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}?](#elastic-ip-address)
44
44
45
45
**Collected metrics and data in AutoOps for self-managed clusters**
@@ -59,6 +59,9 @@ $$$autoops-deployment-types$$$**Where is AutoOps available?**
59
59
$$$cant-see-autoops$$$**Why can't I see AutoOps in some deployments and projects?**
60
60
AutoOps is rolling out in phases across CSPs and [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md), so you may not see it if your deployment or project is in a region where AutoOps is not available yet. AutoOps is currently not available in Azure and GCP.
61
61
62
+
$$$autoops-air-gapped$$$**Can I use AutoOps if my environment is air-gapped?**
63
+
: Not at this time. AutoOps is currently only available as a cloud service and you need an internet connection to send metrics to {{ecloud}}. For air-gapped environments, we plan to offer a locally deployable version in the future.
64
+
62
65
$$$autoops-license$$$**How is AutoOps licensed?**
63
66
: For {{ech}} deployments and {{serverless-short}} projects, AutoOps is available to {{ecloud}} customers at all subscription levels at no additional cost, and it does not consume ECU.
$$$autoops-air-gapped$$$**Can I use AutoOps for my clusters if my environment is air-gapped?**
106
-
: Not at this time. AutoOps is currently only available as a cloud service and you need an internet connection to send metrics to {{ecloud}}. For air-gapped environments, we plan to offer a locally deployable version in the future.
107
-
108
-
$$$macos-install$$$**Can I use macOS to install {{agent}} for this feature?**
109
-
: macOS is not a supported platform for installing {{agent}} and connecting your clusters to AutoOps.
108
+
$$$macos-install$$$**Can I use macOS to set up AutoOps for my self-managed clusters?**
109
+
: No, macOS is not a supported platform for setting up and connecting to AutoOps in a self-managed production environment. However, you can use macOS to [connect your local development cluster to AutoOps](/deploy-manage/monitor/autoops/cc-connect-local-dev-to-autoops.md).
110
110
111
111
$$$elastic-ip-address$$$**Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}?**
112
112
: You may need to define an IP address if your organization’s settings will block the agent from sending out data.
0 commit comments