Skip to content

v0.4.0
Compare
Choose a tag to compare
@Ranjandas Ranjandas released this 12 Jul 02:32
· 15 commits to main since this release
v0.4.0
0ab8b46
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Release Notes

Adds Scenario name to the list output

Every scenario template now adds SHIKARI_SCENARIO_NAME environment variable, which is populated in the list output. This helps identify what scenario a cluster is created with.

$ shikari list
CLUSTER       VM NAME            STATUS        SCENARIO                      DISK(GB)       MEMORY(GB)       CPUS       IMAGE
nomad         nomad-cli-01       Running       nomad-consul-quickstart       100            4                4          <snip>
nomad         nomad-srv-01       Running       nomad-consul-quickstart       100            4                4          <snip>

ref: #47

Adds K3S product for env subcommand

With the introduction of Kubernetes Scenarios using K3S, the env sub-command now supports K3S product.
When k3s is specified as the product, Shikari copies the kubeconfig file from the first server (<cluster-name>-srv-01) of the cluster to the VMs directory (~/.lima/<cluster-name>-srv-01), and prints the KUBECONFIG environment variable with the path set to the config file.

$ shikari list -n kube
CLUSTER       VM NAME           STATUS        SCENARIO            DISK(GB)       MEMORY(GB)       CPUS       IMAGE
kube          kube-cli-01       Running       k3s-multinode       100            4                4          <snip>
kube          kube-srv-01       Running       k3s-multinode       100            4                4          <snip>

$ shikari env -n kube k3s
export KUBECONFIG=/Users/ranjan/.lima/kube-srv-01/k3s.yaml

ref: #50

Adds CACERT variables for all products for TLS scenarios

As we didn’t have the CA Certificates (generated at bake time) used by the products on the host, we resorted to SKIP_VERIFY variables when accessing HTTPS API/UI endpoints.
With this new feature, Shikari sets the CACERT environment variable when the env command is invoked with --tls. Shikari expects the CA certificate to be available inside the first VMs directory under copied-from-guest/<product>-agent-ca.pem

$ shikari env -n secure vault --tls
export VAULT_ADDR=https://192.168.105.60:8200
export VAULT_CACERT=/Users/ranjan/.lima/secure-srv-01/copied-from-guest/vault-agent-ca.pem

$ shikari env -n secure nomad --tls
export NOMAD_ADDR=https://192.168.105.60:4646
export NOMAD_CACERT=/Users/ranjan/.lima/secure-srv-01/copied-from-guest/nomad-agent-ca.pem

ref: #51

Changelog

  • d75158a Add CACERT variables for env subcommand (#51)
  • 350e2a2 Add ImagePath to List Output (#35)
  • f5454bc Add K3S to env subcommand to use with K3S scenarios
  • 1f7735b Add scenario name to the list output (#47)
Assets 8
Loading