Skip to content
This repository has been archived by the owner on Feb 27, 2023. It is now read-only.

Commit

Permalink
nit team1 not team
Browse files Browse the repository at this point in the history
Signed-off-by: Ross Kukulinski <[email protected]>
  • Loading branch information
rosskukulinski committed Jul 12, 2018
1 parent 24a9c3f commit d266ae3
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/route.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ The core of Gimbal is IngressRoutes, which allow traffic to be routed into one o

Before beginning it is important to understand how service discovery functions within Gimbal. The Discoverer components should be deployed per upstream cluster. Once synchronized, services will show up in your team namespace with the cluster name appended.

For example, if a Kubernetes cluster is being discovered and there was a service named `s1` which existed in the namespace `team1`, in the cluster `cluster1`, once synchronized, the service in the Gimbal cluster would be named `cluster1-s1` and it would be in the `team` namespace.
For example, if a Kubernetes cluster is being discovered and there was a service named `s1` which existed in the namespace `team1`, in the cluster `cluster1`, once synchronized, the service in the Gimbal cluster would be named `cluster1-s1` and it would be in the `team1` namespace.

## Basic Routex

Expand Down

0 comments on commit d266ae3

Please sign in to comment.