rpi.carlosedp.cluster-monit.../vars.jsonnet
Carlos de Paula bed566c8c5 Improve Ingress generation from #29
Add TLS to ingress as an optional feature and also be able to provide
own certificates.
2020-03-02 16:46:38 -03:00

60 lines
1.4 KiB
Plaintext

{
_config+:: {
namespace: 'monitoring'
},
// Enable or disable additional modules
modules: [
{
name: 'armExporter',
enabled: false,
file: import 'arm_exporter.jsonnet',
},
{
name: 'upsExporter',
enabled: false,
file: import 'ups_exporter.jsonnet',
},
{
name: 'metallbExporter',
enabled: false,
file: import 'metallb.jsonnet',
},
{
name: 'traefikExporter',
enabled: false,
file: import 'traefik.jsonnet',
},
{
name: 'elasticExporter',
enabled: false,
file: import 'elasticsearch_exporter.jsonnet',
},
],
k3s: {
enabled: false,
master_ip: ['192.168.164.120']
},
// Domain suffix for the ingresses
suffixDomain: '192.168.99.100.nip.io',
// If TLSingress is true, a self-signed HTTPS ingress with redirect will be created
TLSingress: true,
# If UseProvidedCerts is true, provided files will be used on created HTTPS ingresses.
# Use a wildcard certificate for the domain like ex. "*.192.168.99.100.nip.io"
UseProvidedCerts: false,
TLSCertificate: importstr 'server.crt',
TLSKey: importstr 'server.key',
// Setting these to false, defaults to emptyDirs
enablePersistence: {
prometheus: false,
grafana: false,
},
// Grafana "from" email
grafana: {
from_address: 'myemail@gmail.com',
},
}