Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • config-watcher
  • db-refresh-scripts
  • update-runner-setup
  • debug-rabbitmq
  • gamma-test-r20220209_2023
  • gamma-test-r20220209_1951
  • gamma-test-r20220207_2132
  • aws-r20220126_1847 protected
  • aws-r20220126_1817 protected
  • aws-r20220126_1739 protected
  • gamma-test-r20220120_1612
  • gamma-test-r20220120_0213
  • gamma-test-r20220120_0137
  • gamma-test-r20220120_0120
  • gamma-test-r20220120_0044
  • gamma-test-r20220119_2310
  • gamma-test-r20220119_2304
  • gamma-test-r20220119_2201
  • gamma-test-r20220119_2143
  • gamma-test-r20220119_2118
  • gamma-test-r20220119_2024
  • gamma-test-r20220119_2007
  • gamma-test-r20220119_1945
  • gamma-test-r20220119_1929
25 results
Blame Permalink
To learn more about this project, read the wiki.
README.md 2.86 KiB

Cluster Resource Administration

This directory includes Kubernetes resources that should be installed on Kubernetes clusters that will have GeoSphere deployed on them. While there may be local cluster builtin equivalents to the resources defined here, these builtin names are not used in the current configuration in this deploy repository. The builtin resources could be used instead of installing the resources defined in this directory by updating the values-X.yaml files in the various directories and in the .gitlab-ci.yml configuration file.

k3s - Local Path Configuration

When running on a K3S-based (rancher) cluster like the one currently running on kubekorner.ssec.wisc.edu, the local path provisioner should be updated to point to larger storage paths. The K3S cluster software comes with a local path provisioner as the default storage provisioner. This means that when an application asks for generic storage (PersistentVolumeClaim), this provisioner will be used to find and provide the storage. However, by default this provisioner is configured to give access to /var/lib/rancher/k3s/storage which is typically space limited.

By modifying the config.json stored in the local-path-config ConfigMap, we can tell the provisioner where storage should be provided from for each node. See https://github.com/rancher/local-path-provisioner/blob/master/README.md#configuration for more information.

To apply:

echo -e "data:\n  config.json: |-" > tmp.yaml
cat k3s-local-path-config.json | awk '{ print "    " $0 }' >> tmp.yaml
# dry run
kubectl patch -n kube-system cm/local-path-config --type merge --patch "$(cat tmp.yaml)" --dry-run=client
# not dry run
kubectl patch -n kube-system cm/local-path-config --type merge --patch "$(cat tmp.yaml)"

Storage - Local Large Cache

DEPRECATED: See local path provisioner above.

This storage class and persistent volume can be used for cases where a GeoSphere component needs relatively high performance and large capacity storage. Both the StorageClass and the PersistentVolume are defined in local-large-cache.yaml. This storage is primarily used for GeoSphere's tile cache (used by MapCache). It defines large storage that is physically located/connected to the node where the pod is being run or at least performs like it is. The term "large" here refers to multiple terabytes (3-10TB). While this isn't large in generic storage terms, it is considered large for a "cache" which is not guaranteed to persist.

To apply:

kubectl apply -f local-large-cache.yaml

To delete (make unavailable):

kubectl delete pv/local-large-cache
kubectl delete sc/local-large-cache

Storage - Local Medium Archive

DEPRECATED: See local path provisioner above.

Similar to Local Large Cache above, but larger available space. Note this should only be used for testing as data will be deleted when the claim is removed.