Skip to content
Snippets Groups Projects
  1. Oct 24, 2019
  2. Sep 24, 2019
  3. Aug 09, 2019
  4. Jul 31, 2019
  5. Jul 18, 2019
  6. Jul 01, 2019
  7. May 29, 2019
  8. Mar 13, 2019
  9. Feb 14, 2019
  10. Jan 25, 2019
  11. Jan 17, 2019
  12. Jan 11, 2019
  13. Nov 28, 2018
  14. Oct 26, 2018
  15. Jul 17, 2018
  16. Jun 25, 2018
  17. Apr 28, 2018
  18. Apr 13, 2018
  19. Jan 19, 2018
  20. Jan 15, 2018
  21. Jan 05, 2018
  22. Oct 30, 2017
    • Svend Sorensen's avatar
      Omit static compute resource requests and limits from deployment · 73e3dffa
      Svend Sorensen authored
      Do not specify static resource settings in the kubernetes-deployment to avoid
      unnecessary replacement of pods when the manifest is reapplied (`kubectl
      apply`).
      
      The addon-resizer will dynamically set the pod compute resource values. If the
      values are also set statically in the deployment configuration, reapplying the
      configuration will result in the pods getting replaced. Without the static
      resource, the deployment configuration can be reapplied, and the pods will not
      be replaced.
      
      This change was also made in the upstream kube-state-metrics example manifests.
      
      https://github.com/kubernetes/kube-state-metrics/pull/285
      73e3dffa
  23. Aug 28, 2017
  24. Aug 22, 2017
  25. May 17, 2017
  26. May 04, 2017
  27. Apr 10, 2017
  28. Mar 23, 2017
  29. Mar 10, 2017
  30. Mar 07, 2017
  31. Mar 06, 2017
  32. Mar 03, 2017
  33. Feb 28, 2017
  34. Oct 19, 2016
  35. Oct 18, 2016
Loading