2 minute read
Thanos is an opensource Prometheus setup that allows having 2 important features:
- High availability on Prometheus (setting more Prometheus replicas).
- Long term storage capacity relying on external object storage.
This is the simplified diagram of a Thanos architecture:
Image repository and tag
- Thanos components versions:
- Thanos components image:
Setup in Fury Module
We designed 2 different possible setups accordingly with the 2 features listed above:
thanos #this is the setup with only high-availability feature thanos-with-store #this include the storing feature with an object storage thanos-components #this directory contains all the thanos components and is intended to not be used directly
So, you’ll need to add to your
thanos-with-store depending on your needs.
thanos-with-store is a superset that includes also the high availability feature.
Due to the integration with Prometheus, you have to manually patch some resources to make Thanos work properly.
Prometheus CRD Patch
just create a patch like this that will contain the
apiVersion: monitoring.coreos.com/v1 kind: Prometheus metadata: name: k8s namespace: monitoring spec: nodeSelector: asg_role: infra version: v2.27.1 retention: 15d externalUrl: 'https://prometheus-example.example.com/' externalLabels: k8s_cluster: <your cluster name> thanos: baseImage: thanosio/thanos version: v0.20.2 objectStorageConfig: name: thanos key: config
Thanos discovery config file
Depending on the number of replicas you choose in the Prometheus section, you’ll need to patch the configuration of the query component (see here) accordingly to keep it aware of the existing services:
- Prometheus single replica:
# Store targets for thanos-query to use for searching - targets: # Prometheus sidecars for the short term metrics - 'prometheus-k8s-0.prometheus-operated:10901'
- Prometheus 3 replicas
# Store targets for thanos-query to use for searching - targets: # Prometheus sidecars for the short term metrics - prometheus-k8s-0.prometheus-operated:10901 - prometheus-k8s-1.prometheus-operated:10901 - prometheus-k8s-2.prometheus-operated:10901
Same example can be done for a solution with store, is just to add to the previous examples the line (see here) :
If you choose the
thanos-with-store solution, you need also to add a secretConfigGenerator in your kustomization file with proper values:
secretGenerator: # description: config + credentials for access to object storage # used-by: Prometheus, Thanos Store, Thanos Compact - name: thanos-storage type: Opaque behavior: replace files: - config.yaml=thanos-storage-secret.yaml
you can see an example of the
there is no ingress defined by default, but if you want, you can add something like this:
apiVersion: extensions/v1beta1 kind: Ingress metadata: name: thanos namespace: monitoring annotations: forecastle.stakater.com/expose: "true" forecastle.stakater.com/icon: "https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcRQIi0w9WqMmkCcjgC03kxOFhkdeDuV2UIgKo9xfiugGSjRLxstEw" kubernetes.io/ingress.class: internal nginx.ingress.kubernetes.io/force-ssl-redirect: "true" labels: app: thanos-query spec: rules: - host: thanos.example.com http: paths: - path: "/" backend: serviceName: thanos-query servicePort: http
Was this page helpful?
Glad to hear it! Thanks for letting us know!
Sorry to hear that. Please tell us how we can improve.