For complex issues please use https://discuss.hashicorp.com/c/consul/, https://github.com/hashicorp/consul/issues or https://groups.google.com/forum/#!forum/consul-tool.
Hi Team,
erraform has been successfully initialized!
$ terraform validate -var-file=environment/${CI_ENVIRONMENT_NAME}/variables.tfvars
╷
│ Error: Failed to parse command-line flags
│
│ flag provided but not defined: -var-file
╵
For more help on using this command, run:
terraform validate -help
Please can someone help me, if something i'm missing or is there any change in 0.15.4 version
I noticed that I sometimes get this in consul logs on consul servers and clients:
"2021-06-30T08:10:26.559Z [WARN] agent: grpc: addrConn.createTransport failed to connect to {192.168.20.43:8300 0 hp-03.als <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.20.43:8300: operation was canceled\". Reconnecting..."
Any suggestion what this could be? Otherwise, the cluster seems healthy and all nodes are healthy. I use consul 1.10 on all nodes.
"acl": {
"default_policy": "deny",
"down_policy": "extend-cache",
"enable_token_persistence": true,
"enabled": true,
"token_ttl": "30s",
"tokens": {
"agent": "<redacted>",
"master": "<redacted>",
"replication": "<redacted>"
}
},
"addresses": {
"dns": "127.0.0.1",
"grpc": "127.0.0.1",
"http": "127.0.0.1",
"https": "127.0.0.1"
},
"advertise_addr": "192.168.20.41",
"advertise_addr_wan": "192.168.20.41",
"auto_encrypt": {
"allow_tls": true
},
"bind_addr": "192.168.20.41",
"bootstrap": false,
"bootstrap_expect": 3,
"ca_file": "/etc/consul/certs/consul-agent-ca.pem",
"cert_file": "/etc/consul/certs/server.pem",
"client_addr": "127.0.0.1",
"connect": {
"enabled": true
},
"data_dir": "/data/consul",
"datacenter": "als",
"disable_update_check": false,
"domain": "consul",
"enable_local_script_checks": false,
"enable_script_checks": false,
"encrypt": "<redacted>",
"encrypt_verify_incoming": true,
"encrypt_verify_outgoing": true,
"key_file": "/etc/consul/certs/server-key.pem",
"log_file": "/var/log/consul/consul.log",
"log_level": "INFO",
"log_rotate_bytes": 0,
"log_rotate_duration": "24h",
"log_rotate_max_files": 14,
"performance": {
"leave_drain_time": "5s",
"raft_multiplier": 1,
"rpc_hold_timeout": "7s"
},
"ports": {
"dns": 53,
"grpc": 8502,
"http": 8500,
"https": -1,
"serf_lan": 8301,
"serf_wan": 8302,
"server": 8300
},
"primary_datacenter": "als",
"raft_protocol": 3,
"recursors": [
"8.8.8.8",
"8.8.4.4"
],
"retry_interval": "30s",
"retry_interval_wan": "30s",
"retry_join": [
"192.168.20.41",
"192.168.20.42",
"192.168.20.43"
],
"retry_max": 0,
"retry_max_wan": 0,
"server": true,
"tls_min_version": "tls12",
"tls_prefer_server_cipher_suites": false,
"translate_wan_addrs": false,
"ui": false,
"verify_incoming": true,
"verify_incoming_https": false,
"verify_incoming_rpc": false,
"verify_outgoing": true,
"verify_server_hostname": true
Has anyone here implemented consul mesh gateway across DCs (or multicloud) in prod: https://www.consul.io/docs/connect/gateways/mesh-gateway
https://www.consul.io/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways
https://learn.hashicorp.com/tutorials/consul/service-mesh-gateways?in=consul/developer-mesh
connect.sidecar_service
. Instead it forwards all http requests to the actual web service.