rpi.carlosedp.cluster-monit.../manifests/ingress-prometheus.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: prometheus-k8s
  namespace: monitoring
spec:
  rules:
  - host: prometheus.192.168.15.15.nip.io
    http:
      paths:
      - backend:
          serviceName: prometheus-k8s
          servicePort: web
        path: /
  tls:
  - hosts:
    - prometheus.192.168.15.15.nip.io
Initial import 2018-03-02 01:03:53 +01:00			`apiVersion: extensions/v1beta1`
			`kind: Ingress`
			`metadata:`
New prometheus-operator structure using jsonnet build 2018-12-12 18:18:00 +01:00			`name: prometheus-k8s`
Initial import 2018-03-02 01:03:53 +01:00			`namespace: monitoring`
			`spec:`
			`rules:`
Bump libraries and use kube-rbac-proxy in K3s 2020-03-18 15:13:47 +01:00			`- host: prometheus.192.168.15.15.nip.io`
Initial import 2018-03-02 01:03:53 +01:00			`http:`
			`paths:`
New prometheus-operator structure using jsonnet build 2018-12-12 18:18:00 +01:00			`- backend:`
Initial import 2018-03-02 01:03:53 +01:00			`serviceName: prometheus-k8s`
			`servicePort: web`
New prometheus-operator structure using jsonnet build 2018-12-12 18:18:00 +01:00			`path: /`
Improve Ingress generation from #29 Add TLS to ingress as an optional feature and also be able to provide own certificates. 2020-03-02 20:46:38 +01:00			`tls:`
			`- hosts:`
Bump libraries and use kube-rbac-proxy in K3s 2020-03-18 15:13:47 +01:00			`- prometheus.192.168.15.15.nip.io`