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: added the ability to set resource limits<br>- added the ability to add tags<br>- added the ability to pass blacklisted ports<br>- added the ability to use existing kube secret for access key<br>- schema update for metrics_filter<br>- fixed bug where tolerations were not working (#74)
| <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 |
105
+
| <aname="input_access_key"></a> [access\_key](#input\_access\_key)| Access key used by the IBM Cloud Monitoring agent to communicate with the instance. Either `access_key` or `existing_access_key_secret_name` is required. This value will be stored on a new secret on the cluster if passed. |`string`|`null`| no |
106
+
| <aname="input_add_cluster_name"></a> [add\_cluster\_name](#input\_add\_cluster\_name)| If true, configure the cloud monitoring agent to attach a tag containing the cluster name to all metric data. This tag is added in the format `ibm-containers-kubernetes-cluster-name: cluster_name`. |`bool`|`true`| no |
106
107
| <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
108
| <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.2@sha256:0dcdb6d70bab60dae4bf5f70c338f2feb9daeba514f1b8ad513ed24724c2a04d"`| no |
109
+
| <aname="input_agent_limits_cpu"></a> [agent\_limits\_cpu](#input\_agent\_limits\_cpu)| Specifies the CPU limit for the agent. |`string`|`"1"`| no |
110
+
| <aname="input_agent_limits_memory"></a> [agent\_limits\_memory](#input\_agent\_limits\_memory)| Specifies the memory limit for the agent. |`string`|`"1024Mi"`| no |
111
+
| <aname="input_agent_requests_cpu"></a> [agent\_requests\_cpu](#input\_agent\_requests\_cpu)| Specifies the CPU requested to run in a node for the agent. |`string`|`"1"`| no |
112
+
| <aname="input_agent_requests_memory"></a> [agent\_requests\_memory](#input\_agent\_requests\_memory)| Specifies the memory requested to run in a node for the agent. |`string`|`"1024Mi"`| no |
113
+
| <aname="input_agent_tags"></a> [agent\_tags](#input\_agent\_tags)| Map of tags to associate to all metrics that the agent collects. NOTE: Use the `add_cluster_name` boolean variable to add the cluster name as a tag, e.g `{'environment': 'production'}.`|`map(string)`|`{}`| no |
114
+
| <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. [Learn more](https://cloud.ibm.com/docs/monitoring?topic=monitoring-change_kube_agent#change_kube_agent_block_ports). |`list(number)`|`[]`| no |
108
115
| <aname="input_chart"></a> [chart](#input\_chart)| The name of the Helm chart to deploy. |`string`|`"sysdig-deploy"`| no |
109
116
| <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 |
110
117
| <aname="input_chart_version"></a> [chart\_version](#input\_chart\_version)| The version of the Cloud Monitoring agent helm chart to deploy. |`string`|`"1.85.1"`| no |
@@ -114,12 +121,13 @@ No modules.
114
121
| <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 |
115
122
| <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 |
116
123
| <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 |
124
+
| <aname="input_existing_access_key_secret_name"></a> [existing\_access\_key\_secret\_name](#input\_existing\_access\_key\_secret\_name)| An alternative to using the Sysdig Agent `access_key`. Specify the name of a Kubernetes secret containing an access-key entry. Either `access_key` or `existing_access_key_secret_name` is required. |`string`|`null`| no |
117
125
| <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
126
| <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 |
119
127
| <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
128
| <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
129
| <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.2@sha256:a6b301f24557c5e14ab5abe62577340e7ab33ce11f33cfcd4797296d1603184a"`| no |
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 |
130
+
| <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/> include = optional(string)<br/> exclude = optional(string)<br/> }))</pre> |`[]`| no |
123
131
| <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 |
124
132
| <aname="input_namespace"></a> [namespace](#input\_namespace)| Namespace where to deploy the Cloud Monitoring agent. Default value is 'ibm-observe' |`string`|`"ibm-observe"`| no |
125
133
| <aname="input_tolerations"></a> [tolerations](#input\_tolerations)| List of tolerations to apply to Cloud Monitoring agent. | <pre>list(object({<br/> key = optional(string)<br/> operator = optional(string)<br/> value = optional(string)<br/> effect = optional(string)<br/> tolerationSeconds = optional(number)<br/> }))</pre> | <pre>[<br/> {<br/> "operator": "Exists"<br/> },<br/> {<br/> "effect": "NoSchedule",<br/> "key": "node-role.kubernetes.io/master",<br/> "operator": "Exists"<br/> }<br/>]</pre> | no |
# example of how to include / exclude metrics - more info https://cloud.ibm.com/docs/monitoring?topic=monitoring-change_kube_agent#change_kube_agent_log_metrics
109
-
metrics_filter=[{ type ="exclude", name ="metricA.*" }, { type ="include", name ="metricB.*" }]
110
-
container_filter=[{ type ="exclude", parameter ="kubernetes.namespace.name", name ="kube-system" }]
107
+
access_key=module.cloud_monitoring.access_key
111
108
cloud_monitoring_instance_region=var.region
109
+
# example of how to include / exclude metrics - more info https://cloud.ibm.com/docs/monitoring?topic=monitoring-change_kube_agent#change_kube_agent_log_metrics
110
+
metrics_filter=[{ exclude ="metricA.*" }, { include ="metricB.*" }]
111
+
container_filter=[{ type ="exclude", parameter ="kubernetes.namespace.name", name ="kube-system" }]
0 commit comments