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: README.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
@@ -111,7 +111,7 @@ No modules.
111
111
| <aname="input_access_key"></a> [access\_key](#input\_access\_key)| Access key used by the agent to communicate with the instance. Either `access_key` or `existing_access_key_secret_name` is required. This value will be stored in a new secret on the cluster if passed. If you want to use this agent for only metrics or metrics with security and compliance, use a manager key scoped to the IBM Cloud Monitoring instance. If you only want to use the agent for security and compliance use a manager key scoped to the Security and Compliance Center Workload Protection instance. |`string`|`null`| no |
112
112
| <aname="input_add_cluster_name"></a> [add\_cluster\_name](#input\_add\_cluster\_name)| If true, configure the agent to associate a tag containing the cluster name. This tag is added in the format `ibm-containers-kubernetes-cluster-name: cluster_name`. |`bool`|`true`| no |
113
113
| <aname="input_agent_image_repository"></a> [agent\_image\_repository](#input\_agent\_image\_repository)| The image repository to pull the agent image from. |`string`|`"agent-slim"`| no |
114
-
| <aname="input_agent_image_tag_digest"></a> [agent\_image\_tag\_digest](#input\_agent\_image\_tag\_digest)| The image tag or digest of agent image to use. If using digest, it must be in the format of `X.Y.Z@sha256:xxxxx`. |`string`|`"14.2.3@sha256:cb2c437afde546554e04dbc018c125c6ffb60a9878ce6b45a29d769d91782c4b"`| no |
114
+
| <aname="input_agent_image_tag_digest"></a> [agent\_image\_tag\_digest](#input\_agent\_image\_tag\_digest)| The image tag or digest of agent image to use. If using digest, it must be in the format of `X.Y.Z@sha256:xxxxx`. |`string`|`"14.2.4@sha256:c8e6924999390de58471c2ac82b211a0207a50047a1bd15654a678f2b3d1e26e"`| no |
115
115
| <aname="input_agent_limits_cpu"></a> [agent\_limits\_cpu](#input\_agent\_limits\_cpu)| Specify CPU resource limits for the agent. For more info, see https://cloud.ibm.com/docs/monitoring?topic=monitoring-resource_requirements|`string`|`"1"`| no |
116
116
| <aname="input_agent_limits_memory"></a> [agent\_limits\_memory](#input\_agent\_limits\_memory)| Specify memory resource limits for the agent. For more info, see https://cloud.ibm.com/docs/monitoring?topic=monitoring-resource_requirements|`string`|`"1024Mi"`| no |
117
117
| <aname="input_agent_requests_cpu"></a> [agent\_requests\_cpu](#input\_agent\_requests\_cpu)| Specify CPU resource requests for the agent. For more info, see https://cloud.ibm.com/docs/monitoring?topic=monitoring-resource_requirements|`string`|`"1"`| no |
@@ -120,7 +120,7 @@ No modules.
120
120
| <aname="input_blacklisted_ports"></a> [blacklisted\_ports](#input\_blacklisted\_ports)| To block network traffic and metrics from network ports, pass the list of ports from which you want to filter out any data. For more info, see https://cloud.ibm.com/docs/monitoring?topic=monitoring-change_agent#ports|`list(number)`|`[]`| no |
121
121
| <aname="input_chart"></a> [chart](#input\_chart)| The name of the Helm chart to deploy. Use `chart_location` to specify helm chart location. |`string`|`"sysdig-deploy"`| no |
122
122
| <aname="input_chart_location"></a> [chart\_location](#input\_chart\_location)| The location of the agent helm chart. |`string`|`"https://charts.sysdig.com"`| no |
123
-
| <aname="input_chart_version"></a> [chart\_version](#input\_chart\_version)| The version of the agent helm chart to deploy. |`string`|`"1.96.0"`| no |
123
+
| <aname="input_chart_version"></a> [chart\_version](#input\_chart\_version)| The version of the agent helm chart to deploy. |`string`|`"1.96.4"`| no |
124
124
| <aname="input_cluster_config_endpoint_type"></a> [cluster\_config\_endpoint\_type](#input\_cluster\_config\_endpoint\_type)| Specify which type of endpoint to use for for cluster config access: 'default', 'private', 'vpe', 'link'. 'default' value will use the default endpoint of the cluster. |`string`|`"default"`| no |
125
125
| <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 |
126
126
| <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 |
@@ -142,7 +142,7 @@ No modules.
142
142
| <aname="input_instance_region"></a> [instance\_region](#input\_instance\_region)| The region of the IBM Cloud Monitoring instance that you want to send metrics to. The region value is used to construct the ingestion and api endpoints. If you are only using the agent for security and compliance monitoring, set this to the region of your IBM Cloud Security and Compliance Center Workload Protection instance. If you have both Cloud Monitoring and Security and Compliance Center Workload Protection instances, the instances must be connected and must be in the same region to use the same agent. |`string`| n/a | yes |
143
143
| <aname="input_is_vpc_cluster"></a> [is\_vpc\_cluster](#input\_is\_vpc\_cluster)| Specify true if the target cluster is a VPC cluster, false if it is a classic cluster. |`bool`|`true`| no |
144
144
| <aname="input_kernel_module_image_repository"></a> [kernel\_module\_image\_repository](#input\_kernel\_module\_image\_repository)| The image repository to pull the agent kernel module initContainer image from. |`string`|`"agent-kmodule"`| no |
145
-
| <aname="input_kernel_module_image_tag_digest"></a> [kernel\_module\_image\_tag\_digest](#input\_kernel\_module\_image\_tag\_digest)| The image digest to use for the agent kernel module used by the initContainer. Must be in the format of `X.Y.Z@sha256:xxxxx`|`string`|`"14.2.3@sha256:78c87643d1336efa62f4af8af80290f76097fde51c8d8204a5eb38d73363489d"`| no |
145
+
| <aname="input_kernel_module_image_tag_digest"></a> [kernel\_module\_image\_tag\_digest](#input\_kernel\_module\_image\_tag\_digest)| The image digest to use for the agent kernel module used by the initContainer. Must be in the format of `X.Y.Z@sha256:xxxxx`|`string`|`"14.2.4@sha256:767f60e89821228b5a6a30dc91b343609de511abfaf3647d91bf85dc4968cedd"`| no |
146
146
| <aname="input_max_surge"></a> [max\_surge](#input\_max\_surge)| The number of pods that can be created above the desired amount of daemonset pods during an update. If `max_surge` is set to null, the `max_surge` setting is ignored. The variable accepts absolute number or percentage value(e.g., '1' or '10%'). |`string`|`null`| no |
147
147
| <aname="input_max_unavailable"></a> [max\_unavailable](#input\_max\_unavailable)| The maximum number of pods that can be unavailable during a DaemonSet rolling update. Accepts absolute number or percentage (e.g., '1' or '10%'). |`string`|`"1"`| no |
148
148
| <aname="input_metrics_filter"></a> [metrics\_filter](#input\_metrics\_filter)| To filter custom metrics you can specify which metrics to include and exclude. For more info, see https://cloud.ibm.com/docs/monitoring?topic=monitoring-change_kube_agent#change_kube_agent_inc_exc_metrics| <pre>list(object({<br/> include = optional(string)<br/> exclude = optional(string)<br/> }))</pre> |`[]`| no |
0 commit comments