Add translations for topology-mterics and transparent-proxy components

This commit is contained in:
kenia 2021-04-12 16:45:37 -04:00
parent 672c0a818e
commit 31840e6c34
2 changed files with 48 additions and 2 deletions

View File

@ -5,12 +5,12 @@
as |notice|> as |notice|>
<notice.Header> <notice.Header>
<h3> <h3>
Limited Access {{t "components.consul.topology-metrics.notice.limited-access.header"}}
</h3> </h3>
</notice.Header> </notice.Header>
<notice.Body> <notice.Body>
<p> <p>
This service may have dependencies you wont see because you dont have access to them. {{t "components.consul.topology-metrics.notice.limited-access.body"}}
</p> </p>
</notice.Body> </notice.Body>
</Notice> </Notice>

View File

@ -184,6 +184,52 @@ components:
name: Precedence name: Precedence
asc: Ascending asc: Ascending
desc: Descending desc: Descending
transparent-proxy: Transparent Proxy
topology-metrics:
source-type:
tooltip: This connection was defined in a proxy registration.
text: Defined in proxy registration
notice:
limited-access:
header: Limited Access
body: This service may have dependencies you wont see because you dont 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:
name: Edit intentions
URL: dc.services.show.intentions
not-defined-intention:
header: Connections are not explicitly defined
body: There appears to be an Intention defining traffic, but the services are unable to communicate until that connection is explicitly defined as a downstream or Transparent Proxy mode is turned on.
footer:
name: Read the documentation
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:
name: Edit intentions
URL: dc.services.show.intentions
popover:
l7:
header: Layer 7 permissions
body: Certain HTTP request info must be identified.
action: View
deny:
header: Connection Denied
body:
isExact: Change the action of this intention to allow.
notExact: Add an intention that allows these two services to connect.
action:
isExact: Allow
notExact: Create
undefined:
header: No traffic
body: Add the current service as an explicit upstream or turn on Transparent Proxy mode to initiate traffic.
action: Documentation
models: models:
auth-method: auth-method: