Skip to content

Commit 2252920

Browse files
committed
add in warning and note about mTLS enabled
1 parent 5c4ecb4 commit 2252920

File tree

2 files changed

+31
-4
lines changed

2 files changed

+31
-4
lines changed

jekyll/_cci2/server-3-install.adoc

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -88,10 +88,6 @@ cat /etc/letsencrypt/live/<CIRCLECI_SERVER_DOMAIN>/fullchain.pem
8888

8989
* *Private Load Balancer (optional)* - Load balancer doesn't generate external IP addresses.
9090

91-
==== Postgres, MongoDB, Vault settings
92-
93-
You can skip these sections unless you plan on using an existing Postgres, MongoDB or Vault instance, in which case see the https://circleci.com/docs/2.0/server-3-operator-externalizing-services/[Externalizing Services doc]. By default CirecleCI server will create its own Postgres, MongoDB and Vault instances within the CircleCI namespace. The instances inside the CircleCI namespace will be included in the CircleCI backup and restore process.
94-
9591
==== Artifact and Encryption Signing Settings
9692
Encryption and artifact signing keys were created during prerequisites phase. You can enter them here now.
9793

@@ -150,6 +146,13 @@ A JSON format key of the Service Account to use for bucket access.
150146
* *Storage Object Expiry (optional)* -
151147
Number of days to retain your test results and artifacts. Set to 0 to disable and retain objects indefinitely.
152148

149+
==== Nomad
150+
Set nTKLS to disabled. This should be disabled by default but there is a known issue currently preventing this. Disabling allows you to ignore Nomad settings until phase 3 of the installation process where we will install build services.
151+
152+
==== Postgres, MongoDB, Vault settings
153+
154+
You can skip these sections unless you plan on using an existing Postgres, MongoDB or Vault instance, in which case see the https://circleci.com/docs/2.0/server-3-operator-externalizing-services/[Externalizing Services doc]. By default CirecleCI server will create its own Postgres, MongoDB and Vault instances within the CircleCI namespace. The instances inside the CircleCI namespace will be included in the CircleCI backup and restore process.
155+
153156
==== Save and Deploy
154157
Once you have completed the fields detailed above it is time to deploy. The deployment will install the core services and provide you an IP address for the Traefik load balancer. That IP address will be critical in setting up a DNS record and completing the first phase of the installation.
155158

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

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -81,10 +81,34 @@ The new Traefik pos will then start ot schedule correctly.
8181

8282
=== New features
8383

84+
* Customers who require a fully private installation can now access a setting in the KOTS admin console to ensure public IPs are not assigned to VMs. Note that with this non-public IP setting enabled, a work-around will be needed if SSH access to running jobs is required, for example, by using a VPN into your VPC.
85+
* Customers that manage outbound traffic through a proxy can now configure proxy settings through the KOTS admin console. Please see our documentation for specifics on https://circleci.com/docs/2.0/server-3-operator-proxy/[proxy support for server].
86+
* We have expanded the machine build environment options available to include additional resource classes, sizes, and executors. You now have access to Arm (medium, large), Linux (medium, large, X large, and XX large), and Windows (medium, large, XX large) resource classes.
87+
* The https://circleci.com/docs/2.0/insights/[insights API] is now available to all server customers. Leverage build and other data to better understand the performance of teams and the health of your build and testing efforts.
88+
* We have revamped the admin UI, and updated our installation instructions, making it easier to set up and manage server.
89+
* You can now supply a custom Linux AMI for VM service.
90+
* SSL termination can now be disabled - If you have put server login behind a firewall, this will enable SSL termination at the firewall.
91+
* You can now control the size of persistent volumes. For larger customers, the initial persistent volume size was too small, by default. You can now set this at install time, providing an easier migration for those customers that require it. For further information see the https://circleci.com/docs/2.0/server-3-operator-extending-internal-volumes/[Internal Database Volume Expansion doc].
92+
* We have added an auto-scaling example to the https://github.com/CircleCI-Public/server-terraform/blob/main/nomad-aws/main.tf[nomad client terraform].
93+
* You can now choose to serve 'unsafe' build artifacts. Previously this option was hidden, meaning potentially unsafe artifacts were rendered as plain text. For more information see the https://circleci.com/docs/2.0/server-3-operator-build-artifacts/[Build Artifacts doc].
94+
8495
=== Fixes
8596

97+
* The default windows executor was not as documented, we have increased the size to align with documentation and cloud.
98+
8699
=== Known issues
87100

101+
* KOTS admin configuration incorrectly selects the Nomad mTLS as `enabled` during setup. It should be set to mTLS `disabled` until after nomad clients have been deployed.
102+
* 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.
103+
* It is currently possible for multiple organizations under the same CircleCI server account to have contexts with
104+
identical names. This should be avoided as doing so could lead to errors and unexpected behavior.
105+
* 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
106+
application to indicate the cause of the issue. If a build is run on your installation and does not show up in the
107+
CircleCI application, users should be directed to use the https://circleci.com/docs/2.0/local-cli/[CircleCI CLI] to validate the project configuration
108+
and get details of the possible cause of the issue.
109+
* 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.
110+
* Runner cannot be used when server is installed behind a proxy.
111+
88112
== Release 3.1.0
89113

90114
=== Upgrade notes

0 commit comments

Comments
 (0)