Skip to content
  1. Aug 30, 2017
    • Maxim Krasilnikov's avatar
      Change single Vault pki mount to multi pki mounts paths for etcd and kube CA`s (#1552) · 6eb22c5d
      Maxim Krasilnikov authored
      * Added update CA trust step for etcd and kube/secrets roles
      
      * Added load_balancer_domain_name to certificate alt names if defined. Reset CA's in RedHat os.
      
      * Rename kube-cluster-ca.crt to vault-ca.crt, we need separated CA`s for vault, etcd and kube.
      
      * Vault role refactoring, remove optional cert vault auth because not not used and worked. Create separate CA`s fro vault and etcd.
      
      * Fixed different certificates set for vault cert_managment
      
      * Update doc/vault.md
      
      * Fixed condition create vault CA, wrong group
      
      * Fixed missing etcd_cert_path mount for rkt deployment type. Distribute vault roles for all vault hosts
      
      * Removed wrong when condition in create etcd role vault tasks.
      6eb22c5d
  2. Aug 20, 2017
    • Maxim Krasilnikov's avatar
      Fixed deploy cluster with vault cert manager (#1548) · 2ba285a5
      Maxim Krasilnikov authored
      * Added custom ips to etcd vault distributed certificates
      
      * Added custom ips to kube-master vault distributed certificates
      
      * Added comment about issue_cert_copy_ca var in vault/issue_cert role file
      
      * Generate kube-proxy, controller-manager and scheduler certificates by vault
      
      * Revert "Disable vault from CI (#1546)"
      
      This reverts commit 781f31d2.
      
      * Fixed upgrade cluster with vault cert manager
      
      * Remove vault dir in reset playbook
      2ba285a5
  3. Jul 17, 2017
  4. Jun 29, 2017
  5. Apr 19, 2017
  6. Mar 22, 2017
  7. Feb 27, 2017
  8. Feb 18, 2017
  9. Feb 16, 2017
  10. Feb 13, 2017
    • Vladimir Rutsky's avatar
      set "check_mode: no" for read-only "shell" steps that registers result · 09847567
      Vladimir Rutsky authored
      "shell" step doesn't support check mode, which currently leads to failures,
      when Ansible is being run in check mode (because Ansible doesn't run command,
      assuming that command might have effect, and no "rc" or "output" is registered).
      
      Setting "check_mode: no" allows to run those "shell" commands in check mode
      (which is safe, because those shell commands doesn't have side effects).
      09847567
  11. Jan 06, 2017
  12. Jan 02, 2017
  13. Dec 28, 2016
  14. Dec 13, 2016
  15. Dec 09, 2016
Loading