Customize deployment
groundcover supports many custom configurations so you can fit it to the way your deployment works and to your exact needs.
Customize Kubernetes deployment
Our helm chart provides access to many values passed into the chart via the standard values.yaml interface. The deployment can be configured based on most constraints and controls Kubernetes allows around pod assignments to nodes.
groundcover supports most K8s primitives out there, among which:
nodeSelector- a simple form of node selection constraint. You can add thenodeSelectorfield to your Pod specification and specify the node labels you want the target node to have.nodeAffinity- allowing you to constrain which nodes your Pod can be scheduled on based on node labels and is more expressive thannodeSelectorand allows you to specify soft rules.
groundcover supports most K8s primitives out there. Can't find what you need? let us know over Slack.
Override Registry to quay.io
Address potential bandwidth limitations with Amazon ECR Public when using clusters outside of the AWS network.
Quay.io registryDeploy with Argo CD
Argo CD’s multi-environment support ensures that groundcover can be deployed consistently across various Kubernetes clusters.
Argo CDMulti-cluster deployment
Learn how to install groundcover on multiple clusters while using a single, centralized instance of each of these databases.
Multi-cluster deploymentDeploy with an API Key Secret
Deploy groundcover using an API Key Secret ensures that only authorized entities can access the API's functionalities.
API Key SecretFull on-premise deployment
Allows you to use groundcover in secured environments without relying on outbound connections except for authentication purposes.
On-premise deploymentUse host network for Agents communication
Allows the pod to use the host's networking stack for all communication, which means that the pod will use the same IP address as the host.
Agents in host network modeLast updated