Skip to content

Releases: Ranjandas/shikari-scenarios

v0.3.0

15 Jul 06:16
9e76c3c
Compare
Choose a tag to compare

What's Changed

  • Refactor Shikari Variables names to be compatible with v0.3.0 by @Ranjandas in #44
  • Added Shikari Tap to Brewfile by @Ranjandas in #45
  • Add Vault Scenario with Integrated Storage and TLS by @Ranjandas in #46
  • Add Vault Scenario with Consul Storage and TLS by @Ranjandas in #47
  • Add scenario name as env variable by @Ranjandas in #48
  • Added K3S Multi node Scenario by @Ranjandas in #49
  • Patch kubeconfig to have the lima0 IP by @Ranjandas in #50
  • Add environment variable to specify Nomad Node Pool by @Ranjandas in #52
  • Fix a bug in node-pool configuration by @Ranjandas in #53
  • vault integration with nomad by @vijesh12 in #55
  • Integrate WI identity to the nomad-consul-secure scenario by @Ranjandas in #56
  • Update Nomad Scenarios for Multi-DC single Region Support by @Ranjandas in #57
  • Switch to least privileged policy for Nomad Consul token. by @Ranjandas in #59
  • Move the Vault Cert directory to be consistent with other products by @Ranjandas in #62
  • added copyToHost for CACERT copy to host in nomad-consul-secure && vault-integrated and consul storage scenarios by @amitchahalgits in #63
  • HashiCorp Boundary Scenario by @Ranjandas in #64

Full Changelog: v0.2.0...v0.3.0

v0.2.0

28 Jun 02:39
Compare
Choose a tag to compare

⚠️ WARNING: This version only works with Shikari Version v0.2.0 ⚠️

What's Changed

New Contributors

Full Changelog: https://github.com/Ranjandas/shikari-scenarios/commits/v0.2.0