Merge pull request circleci#6624 from circleci/SERVER-1734/server-changelog

Changelog had some erroneous known issues

Author: rosieyohannan

jekyll/_cci2/server-3-whats-new.adoc

@@ -45,8 +45,6 @@ Before upgrading to v3.4.0, delete the deployment named `circleci-server-kube-st
 === Known Issues
 
 * Prometheus is broken in KOTS versions 1.65.0 - 1.67.0. If you rely on this feature, do not upgrade your KOTS version until this issue has been resolved.
-* Updating GitHub Enterprise with a modified Let's Encrypt certificate is unsupported.
-* Let's Encrypt's new root certificate `isrgrootx1` is not trusted.
 * Retry with SSH for jobs using the machine executor advertises a private IP address. For this reason, retry with SSH for jobs using the machine executor works as standard for private installations, but for public installs you would need to ensure that you can access the private IP advertised. For example, by using a VPN into your VPC.
 * CircleCI 1.0 builds are not supported. If an attempt is made to run a 1.0 build, no feedback will be available in the
 application to indicate the cause of the issue. If a build is run on your installation and does not show up in the
@@ -68,8 +66,6 @@ and get details of the possible cause of the issue.
 
 === Known issues
 
-* Updating GitHub Enterprise with a modified Let's Encrypt certificate is unsupported.
-* Let's Encrypt's new root certificate `isrgrootx1` is not trusted.
 * Retry with SSH for jobs using the machine executor advertises a private IP address. For this reason, retry with SSH for jobs using the machine executor works as standard for private installations, but for public installs you would need to ensure that you can access the private IP advertised, for example, by using a VPN into your VPC.
 * CircleCI 1.0 builds are not supported. If an attempt is made to run a 1.0 build, no feedback will be available in the application to indicate the cause of the issue. If a build is run on your installation and does not show up in the CircleCI application, users should be directed to use the https://circleci.com/docs/2.0/local-cli/[CircleCI CLI] to validate the project configuration and get details of the possible cause of the issue.
 * The KOTS Admin Console cannot be upgraded if your installation is set up to be behind a proxy. The proxy settings will be deleted and cause the KOTS Admin Console to break.