dc:
  nodes:
    show:
      healthchecks:
        empty: |
          <p>
            This node has no health checks{items, select,
              0 {}
              other { matching that search}
            }.
          </p>
        critical-serf-notice:
          header: Failing serf check
          body: |
            <p>
              This node has a failing serf node check. The health statuses shown on this page are the statuses as they were known before the node became unreachable.
            </p>
  services:
    show:
      topology:
        notices:
          open: Expand Banners
          close: Collapse Banners
        notice:
          filtered-by-acls:
            header: Limited Access
            body: This service may have dependencies you won’t see because you don’t have access to them.
          default-allow:
            header: Intentions are set to default allow
            body: Your Intention settings are currently set to default allow. This means that this view will show connections to every service in your cluster. We recommend changing your Intention settings to default deny and creating specific Intentions for upstream and downstream services for this view to be useful.
            footer: |
              <p>
                <a href="{route_intentions}">Edit Intentions</a>
              </p>
          wildcard-intention:
            header: Permissive Intention
            body: One or more of your Intentions are set to allow traffic to and/or from all other services in a namespace. This Topology view will show all of those connections if that remains unchanged. We recommend setting more specific Intentions for upstream and downstream services to make this vizualization more useful.
            footer: |
              <p>
                <a href="{route_intentions}">Edit Intentions</a>
              </p>
          not-defined-intention:
            header: Connections are not explicitly defined
            body: There appears to be an Intention allowing traffic, but the services are unable to communicate until that connection is enabled by defining an explicit upstream or proxies are set to 'transparent' mode.
            footer: |
              <p>
                <a href="{CONSUL_DOCS_URL}/connect/registration/service-registration#upstreams" target="_blank" rel="noopener noreferrer">Read the documentation</a>
              </p>
          no-dependencies:
            header: No dependencies
            body: The service you are viewing currently has no dependencies. You will only see metrics for the current service until dependencies are added.
            footer: |
              <p>
                <a href="{CONSUL_DOCS_URL}/connect/registration/service-registration#upstream-configuration-reference" target="_blank" rel="noopener noreferrer">Read the documentation</a>
              </p>
          acls-disabled:
            header: Enable ACLs
            body: This connect-native service may have dependencies, but Consul isn't aware of them when ACLs are disabled. Enable ACLs to make this view more useful.
            footer: |
              <p>
                <a href="{CONSUL_DOCS_URL}/security/acl/acl-system#configuring-acls" target="_blank" rel="noopener noreferrer">Read the documentation</a>
              </p>
      upstreams:
        intro: |
          <p>
            Upstreams are services that may receive traffic from this gateway. If you are not using Consul DNS, please make sure your <code>Host:</code> header uses the correct domain name for the gateway to correctly proxy to its upstreams. Learn more about configuring gateways in our <a href="{CONSUL_DOCS_URL}/connect/ingress-gateways" target="_blank" rel="noopener noreferrer">documentation</a>.
          </p>
    instance:
      healthchecks:
        empty: |
          <p>
            This instance has no health checks{items, select,
              0 {}
              other { matching that search}
            }.
          </p>
        critical-serf-notice:
          header: Failing serf check
          body: |
            <p>
              This instance has a failing serf node check. The health statuses shown on this page are the statuses as they were known before the node became unreachable.
            </p>
      upstreams:
        tproxy-mode:
          header: Transparent proxy mode
          body: The upstreams listed on this page have been defined in a proxy registration. There may be more upstreams, though, as "transparent" mode is enabled on this proxy.
          footer: Read the documentation
  routing-config:
    source: Routing Configuration