Rancher2_cluster_logging resource doesn’t configure log streaming

Rancher
1

Rancher Server Setup

  • Rancher version: 2.6.3
  • Installation option: Helm Chart
  • If Helm Chart, Kubernetes Cluster and version: RKE1
  • Proxy/Cert Details:

Cluster info:

  • Kube version: v1.20.12
  • Cluster type: custom downstream cluster based on EC2 instances.

Hi, we used rancher2_cluster_logging terraform resource to configure log streaming to AWS Opensearch from one of the downstream clusters. terraform apply finished without any issues, but there are no logging configurations in that downstream cluster, and cluster-logging namespace is empty now. At the same moment, local cluster has fluentd related pods in cluster-logging namespace and they are successfully sending logs to OpenSearch.

We’ve checked v3/clusters/foobar/clusterloggings endpoint, and we are found something:

"data": [
      {
      "annotations": { },
      "appliedSpec": {
      "clusterId": "",
      "enableJSONParsing": false,
      "includeSystemComponent": true,
      "outputFlushInterval": 60,
      "type": "/v3/schemas/clusterLoggingSpec"
      },
      "baseType": "clusterLogging",
      "clusterId": "foobar"
      "conditions": [
      {
              "lastUpdateTime": "2022-02-22T12:45:40Z",
              "message": "tls handshake opensearch.foobar.com failed: dial tcp: address opensearch.foobar.com: missing port in address",
              "status": "False",
              "type": "Updated"
      }
],