1. 03 Sep, 2019 1 commit
  2. 24 Aug, 2019 1 commit
  3. 19 Aug, 2019 1 commit
  4. 09 Aug, 2019 1 commit
  5. 31 Jul, 2019 1 commit
  6. 28 Jul, 2019 1 commit
  7. 23 Jul, 2019 1 commit
  8. 20 Jul, 2019 1 commit
  9. 19 Jul, 2019 1 commit
  10. 07 Jul, 2019 1 commit
  11. 04 Jul, 2019 1 commit
  12. 27 Jun, 2019 4 commits
  13. 17 Jun, 2019 1 commit
  14. 09 Jun, 2019 1 commit
  15. 15 May, 2019 2 commits
  16. 14 May, 2019 3 commits
  17. 26 Apr, 2019 1 commit
  18. 22 Apr, 2019 1 commit
  19. 26 Mar, 2019 1 commit
  20. 26 Feb, 2019 1 commit
  21. 09 Feb, 2019 1 commit
  22. 30 Jan, 2019 1 commit
  23. 15 Jan, 2019 1 commit
  24. 14 Jan, 2019 1 commit
  25. 02 Jan, 2019 1 commit
  26. 03 Dec, 2018 2 commits
  27. 09 Nov, 2018 1 commit
  28. 05 Nov, 2018 1 commit
  29. 18 Sep, 2018 1 commit
  30. 17 Sep, 2018 1 commit
  31. 05 Sep, 2018 1 commit
  32. 02 Jul, 2018 1 commit
  33. 21 Jun, 2018 1 commit
    • Ferenc-'s avatar
      [stable/influxdb] Add fullnameOverride (#6224) · 3965be67
      Ferenc- authored
      * Similar to other charts, this allows configurable name
        overrides so 'cleaner' resource names can be achieved,
        which are independent from the wanted release names.
      
      * This is a must have if you want to integrate influxdb with
        other charts, where a resource name can't be templated
        and has to be fixed in the values.yaml, and you have to
        deploy that in multiple instances on the same k8s cluster.
        For example if you have an integration chart and
        the grafana data source URI points to a fixed influxdb
        service name, then without this patch,
        it can't be deployed in multiple instances,
        since the service name depends on the release name,
        which has to be unique.
      3965be67