Skip to content

Consul Connect: Can't connect to a sidecar service from another datacenter after upgrading to Workload Identities #6282

Consul Connect: Can't connect to a sidecar service from another datacenter after upgrading to Workload Identities

Consul Connect: Can't connect to a sidecar service from another datacenter after upgrading to Workload Identities #6282

Triggered via issue October 24, 2024 05:35
Status Success
Total duration 26s
Artifacts

jira-issues.yaml

on: issue_comment
Jira Community Issue sync
17s
Jira Community Issue sync
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Jira Community Issue sync
The following actions use a deprecated Node.js version and will be forced to run on node20: atlassian/gajira-login@45fd029b9f1d6d8926c6f04175aa80c0e42c9026. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/