From f0ae2098134ef571d6ede4137917d2ef76244ac5 Mon Sep 17 00:00:00 2001 From: kjeld Schouten-Lebbing Date: Sun, 15 Aug 2021 12:48:25 +0200 Subject: [PATCH] move some content around --- .../Quick-Start Guides/14-linking-apps.md | 36 +++++++++++++++++++ docs/manual/indepth/linking.md | 33 ----------------- 2 files changed, 36 insertions(+), 33 deletions(-) delete mode 100644 docs/manual/indepth/linking.md diff --git a/docs/manual/Quick-Start Guides/14-linking-apps.md b/docs/manual/Quick-Start Guides/14-linking-apps.md index 214549df3cf..0e93114d918 100644 --- a/docs/manual/Quick-Start Guides/14-linking-apps.md +++ b/docs/manual/Quick-Start Guides/14-linking-apps.md @@ -1,5 +1,37 @@ # 14 - Linking Apps Internally +We often need to connect individual apps together, for example: Sonarr and SABnzbd. This means we first need to know how to reach those Apps. + +##### Linking Apps Internally + +The backend for TrueNAS SCALE Apps is Kubernetes. Linking apps together in Kubernetes is done slightly differently than in other systems, as you can't point directly to other containers using their IP address. + +Instead we need to use their internal(!) domain name. Please beware: this name is only available between Apps and can not be reached from the host/node or your own PC. + +The format for internal domain name for the main service is as follows, please replace `$APPNAME` with the name you gave your App when installing. + +- `$APPNAME.ix-$APPNAME.svc.cluster.local` + +Kubernetes can usually identify the app when omitting `svc.cluster.local` as well: +- `$APPNAME.ix-$APPNAME` + +If you need to reach a different service (which is not often the case!), you need a slightly different format, where `$SVCNAME` is the name of the service you want to reach: + +- `$SVCNAME.ix-$APPNAME.svc.cluster.local` or +- `$SVCNAME.ix-$APPNAME` + +##### Example + +To reach an app named "sabnzbd" within Sonarr, we can use the following internal domain name: + +- `sabnzbd.ix-sabnzbd` + + + + +##### Internal Domain Name generator + +