Skip to content

Commit

Permalink
Readme updates for 1.5.0 (#212)
Browse files Browse the repository at this point in the history
  • Loading branch information
rs-vertica authored Jun 3, 2022
1 parent f0855d1 commit 0cba0b4
Showing 1 changed file with 14 additions and 5 deletions.
19 changes: 14 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -76,14 +76,17 @@ A pod is an ephemeral Kubernetes object that requires access to external storage

For details about local volume mounts, StorageClass requirements, and custom volume mounts, see [Containerized Vertica on Kubernetes](https://www.vertica.com/docs/latest/HTML/Content/Authoring/Containers/Kubernetes/ContainerizedVerticaWithK8s.htm).

# Scale Up and Down
# Scaling Subclusters

Vertica on Kubernetes offers the following two scaling strategies to fine-tune your clusters by workload:
Vertica on Kubernetes manages subclusters by workload, which allows you to fine-tune your workload with one of the following scaling strategies:

- For complex, long-running queries, add nodes to an existing subcluster.
- To increase the throughput of multiple short-term queries (often called "dashboard queries"), improve your cluster's parallelism by adding subclusters.
- Subcluster: Increase the throughput of multiple short-term queries (often called "dashboard queries") to improve your cluster's parallelism.
- Pod: Increase the number of pods in an existing subcluster for complex, long-running queries.

For complete instructions on scaling subclusters, see [Subclusters on Kubernetes](https://www.vertica.com/docs/latest/HTML/Content/Authoring/Containers/Kubernetes/SubclustersOperator.htm).
For details about manually sizing subclusters for new workloads, see [Subclusters on Kubernetes](https://www.vertica.com/docs/latest/HTML/Content/Authoring/Containers/Kubernetes/SubclustersOperator.htm).


After you create a subcluster, you can use the VerticaAutoscaler to automatically scale subclusters or pods when resource metrics reach specified triggers. For instructions on automatically scaling existing subclusters with VerticaAutoscaler, see [VerticaAutoscaler Custom Resource](https://www.vertica.com/docs/latest/HTML/Content/Authoring/Containers/Kubernetes/VerticaAutoScaler.htm).


# Client Connections
Expand Down Expand Up @@ -125,6 +128,12 @@ OpenShift manages security with [Security Context Constraints](https://docs.open

For details about Vertica on OpenShift, see [Red Hat OpenShift Overview](https://www.vertica.com/docs/latest/HTML/Content/Authoring/Containers/Kubernetes/OpenShiftK8s.htm).

# Prometheus Integraion

Vertica integrates with [Prometheus](https://prometheus.io) to collect time series metrics on the VerticaDB operator. Configure Prometheus to authorize connections using a role-based access (RBAC) sidecar proxy, or expose the metrics to external clients with an HTTP endpoint.

For more information, see [Prometheus Integration](https://www.vertica.com/docs/latest/HTML//Content/Authoring/Containers/Kubernetes/Prometheus.htm).

# Additional Details

For additional details on the internals of Vertica, see the [Vertica Documentation](https://www.vertica.com/docs/latest/HTML/Content/Home.htm).
Expand Down

0 comments on commit 0cba0b4

Please sign in to comment.