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
feat: A fix was added which was preventing the image_registry value from being passed to the helm chart, meaning the image was being pulled from quay.io (which would fail if cluster does not have public gateway enabled on all nodes). As part of this fix, the following new variables have been exposed: image_registry_base_url, image_registry_namespace, agent_image_repository, agent_image_tag_digest, kernel_module_image_tag_digest, and kernal_module_image_repository. The image_registry input has been removed.<br>- A fix was added to fix the public ingest endpoint (#64)
| <aname="input_access_key"></a> [access\_key](#input\_access\_key)| Access key used by the IBM Cloud Monitoring agent to communicate with the instance |`string`| n/a | yes |
106
+
| <aname="input_agent_image_repository"></a> [agent\_image\_repository](#input\_agent\_image\_repository)| The image repository to pull the Cloud Monitoring agent image from. |`string`|`"agent-slim"`| no |
107
+
| <aname="input_agent_image_tag_digest"></a> [agent\_image\_tag\_digest](#input\_agent\_image\_tag\_digest)| The image tag digest to use for the Cloud Monitoring agent. |`string`|`"13.9.1@sha256:14860d181a8b712c4150bb59e3ba0ff4be08959e2c45376b32c8eb7ff70461f9"`| no |
106
108
| <aname="input_chart"></a> [chart](#input\_chart)| The name of the Helm chart to deploy. |`string`|`"sysdig-deploy"`| no |
107
109
| <aname="input_chart_location"></a> [chart\_location](#input\_chart\_location)| The location of the Cloud Monitoring agent helm chart. |`string`|`"https://charts.sysdig.com"`| no |
108
110
| <aname="input_chart_version"></a> [chart\_version](#input\_chart\_version)| The version of the Cloud Monitoring agent helm chart to deploy. |`string`|`"1.83.1"`| no |
@@ -112,9 +114,11 @@ No modules.
112
114
| <aname="input_cluster_id"></a> [cluster\_id](#input\_cluster\_id)| The ID of the cluster you wish to deploy the agent in |`string`| n/a | yes |
113
115
| <aname="input_cluster_resource_group_id"></a> [cluster\_resource\_group\_id](#input\_cluster\_resource\_group\_id)| The Resource Group ID of the cluster |`string`| n/a | yes |
114
116
| <aname="input_container_filter"></a> [container\_filter](#input\_container\_filter)| To filter custom containers, specify which containers to include or exclude from metrics collection for the cloud monitoring agent. See https://cloud.ibm.com/docs/monitoring?topic=monitoring-change_kube_agent#change_kube_agent_filter_data.| <pre>list(object({<br/> type = string<br/> parameter = string<br/> name = string<br/> }))</pre> |`[]`| no |
115
-
| <aname="input_image_registry"></a> [image\_registry](#input\_image\_registry)| The image registry to use for the Cloud Monitoring agent. |`string`|`"icr.io/ext/sysdig/agent"`| no |
116
-
| <aname="input_image_tag_digest"></a> [image\_tag\_digest](#input\_image\_tag\_digest)| The image tag digest to use for the Cloud Monitoring agent. |`string`|`"13.9.1@sha256:3193987f77dba930cb22c200df9981afcd097e7cd5885b77d13e20ef353dc5b8"`| no |
117
+
| <aname="input_image_registry_base_url"></a> [image\_registry\_base\_url](#input\_image\_registry\_base\_url)| The image registry base URL to pull the Cloud Monitoring agent images from. For example `icr.io`, `quay.io`, etc. |`string`|`"icr.io"`| no |
118
+
| <aname="input_image_registry_namespace"></a> [image\_registry\_namespace](#input\_image\_registry\_namespace)| The namespace within the image registry to pull the Cloud Monitoring agent images from. |`string`|`"ext/sysdig"`| no |
117
119
| <aname="input_is_vpc_cluster"></a> [is\_vpc\_cluster](#input\_is\_vpc\_cluster)| Specify true if the target cluster for the monitoring agent is a VPC cluster, false if it is a classic cluster. |`bool`|`true`| no |
120
+
| <aname="input_kernal_module_image_repository"></a> [kernal\_module\_image\_repository](#input\_kernal\_module\_image\_repository)| The image repository to pull the Cloud Monitoring agent kernal module initContainer image from. |`string`|`"agent-kmodule"`| no |
121
+
| <aname="input_kernel_module_image_tag_digest"></a> [kernel\_module\_image\_tag\_digest](#input\_kernel\_module\_image\_tag\_digest)| The image tag digest to use for the Cloud Monitoring agent kernel module used by the initContainer. |`string`|`"13.9.1@sha256:0eef614a5988f6979d487f949b3cb1212f8253433057894b5583bf01bf378fb3"`| no |
118
122
| <aname="input_metrics_filter"></a> [metrics\_filter](#input\_metrics\_filter)| To filter custom metrics, specify the Cloud Monitoring metrics to include or to exclude. See https://cloud.ibm.com/docs/monitoring?topic=monitoring-change_kube_agent#change_kube_agent_inc_exc_metrics.| <pre>list(object({<br/> type = string<br/> name = string<br/> }))</pre> |`[]`| no |
119
123
| <aname="input_name"></a> [name](#input\_name)| Cloud Monitoring agent name. Used for naming all kubernetes and helm resources on the cluster. |`string`|`"sysdig-agent"`| no |
120
124
| <aname="input_namespace"></a> [namespace](#input\_namespace)| Namespace where to deploy the Cloud Monitoring agent. Default value is 'ibm-observe' |`string`|`"ibm-observe"`| no |
Copy file name to clipboardExpand all lines: main.tf
+34-5Lines changed: 34 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ data "ibm_container_cluster_config" "cluster_config" {
30
30
locals {
31
31
# LOCALS
32
32
cluster_name=var.is_vpc_cluster? data.ibm_container_vpc_cluster.cluster[0].resource_name: data.ibm_container_cluster.cluster[0].resource_name# Not publically documented in provider. See https://github.com/IBM-Cloud/terraform-provider-ibm/issues/4485
0 commit comments