Commit d1fcca1a authored by Amy Qualls's avatar Amy Qualls

Remove mentions of high availability

Removing mentions of high availability per request from GitLab
executive team.
parent 0895fbbd
...@@ -114,7 +114,7 @@ prometheus['scrape_configs'] = [ ...@@ -114,7 +114,7 @@ prometheus['scrape_configs'] = [
NOTE: **Note:** NOTE: **Note:**
Prometheus and most exporters don't support authentication. We don't recommend exposing them outside the local network. Prometheus and most exporters don't support authentication. We don't recommend exposing them outside the local network.
A few configuration changes are required to allow GitLab to be monitored by an external Prometheus server. External servers are recommended for highly available deployments of GitLab with multiple nodes. A few configuration changes are required to allow GitLab to be monitored by an external Prometheus server. External servers are recommended for [GitLab deployments with multiple nodes](../../reference_architectures/index.md).
To use an external Prometheus server: To use an external Prometheus server:
......
...@@ -933,8 +933,8 @@ vault: ...@@ -933,8 +933,8 @@ vault:
installed: true installed: true
``` ```
By default you will get a basic Vault setup with no high availability nor any scalable By default you will get a basic Vault setup with no scalable
storage backend. This is enough for simple testing and small scale deployments, though has limits storage backend. This is enough for simple testing and small-scale deployments, though has limits
to how much it can scale, and as it is a single instance deployment, you will experience downtime to how much it can scale, and as it is a single instance deployment, you will experience downtime
when upgrading the Vault application. when upgrading the Vault application.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment