]> granicus.if.org Git - icinga2/commitdiff
Docs: Add upgrade note for certs path
authorMichael Friedrich <michael.friedrich@icinga.com>
Thu, 7 Sep 2017 15:01:25 +0000 (17:01 +0200)
committerGunnar Beutner <gunnar.beutner@icinga.com>
Tue, 12 Sep 2017 10:52:49 +0000 (12:52 +0200)
refs #5450

doc/16-upgrading-icinga-2.md

index bc7732acba42652c2360d13294b62cc4a57810b6..e0daff557b8c693a74a53211354a467cb4205136 100644 (file)
@@ -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