From: Michael Friedrich <michael.friedrich@icinga.com>
Date: Thu, 7 Sep 2017 15:01:25 +0000 (+0200)
Subject: Docs: Add upgrade note for certs path
X-Git-Tag: v2.8.0~87^2~6
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=10b8c00d7a0e8128c569cf440a233fccd3b8c7df;p=icinga2

Docs: Add upgrade note for certs path

refs #5450
---

diff --git a/doc/16-upgrading-icinga-2.md b/doc/16-upgrading-icinga-2.md
index bc7732acb..e0daff557 100644
--- a/doc/16-upgrading-icinga-2.md
+++ b/doc/16-upgrading-icinga-2.md
@@ -1,8 +1,20 @@
-#  Upgrading Icinga 2 <a id="upgrading-icinga-2"></a>
+# Upgrading Icinga 2 <a id="upgrading-icinga-2"></a>
 
 Upgrading Icinga 2 is usually quite straightforward. Ordinarily the only manual steps involved
 are scheme updates for the IDO database.
 
+## Upgrading to v2.8 <a id="upgrading-to-2-8"></a>
+
+The default certificate path was changed from `/etc/icinga2/pki` to
+`/var/lib/icinga2/certs`.
+
+This applies to Windows clients in the same way: `%ProgramData%\etc\icinga2\pki`
+was moved to `%ProgramData%`\var\lib\icinga2\certs`.
+
+The [setup CLI commands](06-distributed-monitoring.md#distributed-monitoring-setup-master) and the
+default [ApiListener configuration](06-distributed-monitoring.md#distributed-monitoring-apilistener)
+have been adjusted to these paths too.
+
 ## Upgrading the MySQL database <a id="upgrading-mysql-db"></a>
 
 If you're upgrading an existing Icinga 2 instance, you should check the