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
|[ibm_container_cluster.cluster](https://registry.terraform.io/providers/ibm-cloud/ibm/latest/docs/data-sources/container_cluster)| data source |
87
87
|[ibm_container_cluster_config.cluster_config](https://registry.terraform.io/providers/ibm-cloud/ibm/latest/docs/data-sources/container_cluster_config)| data source |
88
88
|[ibm_container_vpc_cluster.cluster](https://registry.terraform.io/providers/ibm-cloud/ibm/latest/docs/data-sources/container_vpc_cluster)| data source |
@@ -91,29 +91,21 @@ No modules.
91
91
92
92
| Name | Description | Type | Default | Required |
| <aname="input_agent_additional_metadata"></a> [agent\_additional\_metadata](#input\_agent\_additional\_metadata)| The list of additional metadata fields to add to the routed logs. | <pre>list(object({<br/> key = optional(string)<br/> value = optional(string)<br/> }))</pre> |`[]`| no |
95
+
| <aname="input_agent_iam_api_key"></a> [agent\_iam\_api\_key](#input\_agent\_iam\_api\_key)| The IBM Cloud API key for the Logs agent to authenticate and communicate with the IBM Cloud Logs. |`string`| n/a | yes |
96
+
| <aname="input_agent_name"></a> [agent\_name](#input\_agent\_name)| The name of the Logs agent. The name is used in all Kubernetes and Helm resources in the cluster. |`string`|`"logs-agent"`| no |
97
+
| <aname="input_agent_namespace"></a> [agent\_namespace](#input\_agent\_namespace)| The namespace where the Logs agent is deployed. The default value is `ibm-agent`. |`string`|`"ibm-agent"`| no |
| <aname="input_agent_tolerations"></a> [agent\_tolerations](#input\_agent\_tolerations)| List of tolerations to apply to Logs agent. The default value means a pod will run on every node. | <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/>]</pre> | no |
100
+
| <aname="input_chart_location"></a> [chart\_location](#input\_chart\_location)| The location of the Helm chart for the Sysdig agent. |`string`|`"sysdig-deploy"`| no |
101
+
| <aname="input_chart_repository"></a> [chart\_repository](#input\_chart\_repository)| The repository URL for the Sysdig Helm chart. |`string`|`"https://charts.sysdig.com"`| no |
102
+
| <aname="input_chart_version"></a> [chart\_version](#input\_chart\_version)| The version of the Sysdig Helm chart to deploy. |`string`|`"1.14.6"`| no |
94
103
| <aname="input_cloud_logs_ingress_endpoint"></a> [cloud\_logs\_ingress\_endpoint](#input\_cloud\_logs\_ingress\_endpoint)| The host for IBM Cloud Logs ingestion. Ensure you use the ingress endpoint. See https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-endpoints_ingress.|`string`| n/a | yes |
95
-
| <aname="input_cloud_logs_ingress_port"></a> [cloud\_logs\_ingress\_port](#input\_cloud\_logs\_ingress\_port)| The target port for the IBM Cloud Logs ingestion endpoint. The port must be 443 if you connect by using a VPE gateway, or port 3443 when you connect by using CSEs. |`number`|`3443`| no |
96
104
| <aname="input_cluster_config_endpoint_type"></a> [cluster\_config\_endpoint\_type](#input\_cluster\_config\_endpoint\_type)| The type of endpoint to use for the cluster config access: `default`, `private`, `vpe`, or `link`. The `default` value uses the default endpoint of the cluster. |`string`|`"default"`| no |
97
105
| <aname="input_cluster_id"></a> [cluster\_id](#input\_cluster\_id)| The ID of the cluster to deploy the agent. |`string`| n/a | yes |
98
106
| <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 |
99
107
| <aname="input_is_vpc_cluster"></a> [is\_vpc\_cluster](#input\_is\_vpc\_cluster)| Specify true if the target cluster for the agent is a VPC cluster, false if it is a classic cluster. |`bool`|`true`| no |
100
-
| <aname="input_logs_agent_additional_log_source_paths"></a> [logs\_agent\_additional\_log\_source\_paths](#input\_logs\_agent\_additional\_log\_source\_paths)| The list of additional log sources. By default, the Logs agent collects logs from a single source at `/var/log/containers/*.log`. |`list(string)`|`[]`| no |
101
-
| <aname="input_logs_agent_additional_metadata"></a> [logs\_agent\_additional\_metadata](#input\_logs\_agent\_additional\_metadata)| The list of additional metadata fields to add to the routed logs. | <pre>list(object({<br/> key = optional(string)<br/> value = optional(string)<br/> }))</pre> |`[]`| no |
102
-
| <aname="input_logs_agent_chart_location"></a> [logs\_agent\_chart\_location](#input\_logs\_agent\_chart\_location)| The location of the Helm chart for the Logs agent. |`string`|`"oci://icr.io/ibm/observe/logs-agent-helm"`| no |
103
-
| <aname="input_logs_agent_chart_version"></a> [logs\_agent\_chart\_version](#input\_logs\_agent\_chart\_version)| The version of the helm chart to deploy. |`string`|`"1.4.2"`| no |
104
-
| <aname="input_logs_agent_enable_scc"></a> [logs\_agent\_enable\_scc](#input\_logs\_agent\_enable\_scc)| Whether to enable creation of Security Context Constraints in Openshift. When installing on an OpenShift cluster, this setting is mandatory to configure permissions for pods within your cluster. |`bool`|`true`| no |
105
-
| <aname="input_logs_agent_exclude_log_source_paths"></a> [logs\_agent\_exclude\_log\_source\_paths](#input\_logs\_agent\_exclude\_log\_source\_paths)| The list of log sources to exclude. Specify the paths that the Logs agent ignores. |`list(string)`|`[]`| no |
106
-
| <aname="input_logs_agent_iam_api_key"></a> [logs\_agent\_iam\_api\_key](#input\_logs\_agent\_iam\_api\_key)| The IBM Cloud API key for the Logs agent to authenticate and communicate with the IBM Cloud Logs. It is required if `logs_agent_iam_mode` is set to `IAMAPIKey`. |`string`|`null`| no |
107
-
| <aname="input_logs_agent_iam_environment"></a> [logs\_agent\_iam\_environment](#input\_logs\_agent\_iam\_environment)| IAM authentication Environment: `Production` or `PrivateProduction` or `Staging` or `PrivateStaging`. `Production` specifies the public endpoint & `PrivateProduction` specifies the private endpoint. |`string`|`"PrivateProduction"`| no |
108
-
| <aname="input_logs_agent_iam_mode"></a> [logs\_agent\_iam\_mode](#input\_logs\_agent\_iam\_mode)| IAM authentication mode: `TrustedProfile` or `IAMAPIKey`. |`string`|`"TrustedProfile"`| no |
109
-
| <aname="input_logs_agent_log_source_namespaces"></a> [logs\_agent\_log\_source\_namespaces](#input\_logs\_agent\_log\_source\_namespaces)| The list of namespaces from which logs should be forwarded by agent. If namespaces are not listed, logs from all namespaces will be sent. |`list(string)`|`[]`| no |
110
-
| <aname="input_logs_agent_name"></a> [logs\_agent\_name](#input\_logs\_agent\_name)| The name of the Logs agent. The name is used in all Kubernetes and Helm resources in the cluster. |`string`|`"logs-agent"`| no |
111
-
| <aname="input_logs_agent_namespace"></a> [logs\_agent\_namespace](#input\_logs\_agent\_namespace)| The namespace where the Logs agent is deployed. The default value is `ibm-agent`. |`string`|`"ibm-agent"`| no |
| <aname="input_logs_agent_selected_log_source_paths"></a> [logs\_agent\_selected\_log\_source\_paths](#input\_logs\_agent\_selected\_log\_source\_paths)| The list of specific log sources paths. Logs will only be collected from the specified log source paths. If no paths are specified, it will send logs from `/var/log/containers`. |`list(string)`|`[]`| no |
114
-
| <aname="input_logs_agent_tolerations"></a> [logs\_agent\_tolerations](#input\_logs\_agent\_tolerations)| List of tolerations to apply to Logs agent. The default value means a pod will run on every node. | <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/>]</pre> | no |
115
-
| <aname="input_logs_agent_trusted_profile"></a> [logs\_agent\_trusted\_profile](#input\_logs\_agent\_trusted\_profile)| The IBM Cloud trusted profile ID. Used only when `logs_agent_iam_mode` is set to `TrustedProfile`. The trusted profile must have an IBM Cloud Logs `Sender` role. |`string`|`null`| no |
116
-
| <aname="input_logs_agent_version"></a> [logs\_agent\_version](#input\_logs\_agent\_version)| The version of the Logs agent to deploy. |`string`|`"1.4.2"`| no |
108
+
| <aname="input_node_analyzer_enabled"></a> [node\_analyzer\_enabled](#input\_node\_analyzer\_enabled)| Enable or disable the Node Analyzer feature in the Sysdig agent. |`bool`|`true`| no |
117
109
| <aname="input_wait_till"></a> [wait\_till](#input\_wait\_till)| To avoid long wait times when you run your Terraform code, you can specify the stage when you want Terraform to mark the cluster resource creation as completed. Depending on what stage you choose, the cluster creation might not be fully completed and continues to run in the background. However, your Terraform code can continue to run without waiting for the cluster to be fully created. Supported args are `MasterNodeReady`, `OneWorkerNodeReady`, `IngressReady` and `Normal`|`string`|`"Normal"`| no |
118
110
| <aname="input_wait_till_timeout"></a> [wait\_till\_timeout](#input\_wait\_till\_timeout)| Timeout for wait\_till in minutes. |`number`|`90`| no |
# As a `Sender`, you can send logs to your IBM Cloud Logs service instance - but not query or tail logs. This role is meant to be used by agent and routers sending logs.
29
-
trusted_profile_policies=[{
30
-
roles = ["Sender"]
31
-
resources = [{
32
-
service ="logs"
33
-
}]
34
-
}]
35
-
# Set up fine-grained authorization for `logs-agent` running in ROKS cluster in `ibm-agent` namespace.
36
-
trusted_profile_links=[{
37
-
cr_type ="ROKS_SA"
38
-
links = [{
39
-
crn = module.ocp_base.cluster_crn
40
-
namespace = local.logs_agent_namespace
41
-
name = local.logs_agent_name
42
-
}]
17
+
# As a `Sender`, you can send logs to your IBM Cloud Logs service instance - but not query or tail logs. This role is meant to be used by agent and routers sending logs.
18
+
module"iam_service_id" {
19
+
source="terraform-ibm-modules/iam-service-id/ibm"
20
+
version="1.2.0"
21
+
iam_service_id_name="${var.prefix}-service-id"
22
+
iam_service_id_description="Logs Agent service id"
0 commit comments