feat: docusaurus v3.4.0 and asset updates. (#152)

* feat: docusaurus v3.4.0 and asset updates.

* fix(ci): update node to v18

* fix: correct the private repo secret key name that is expected (fixes #150)

.github/workflows/release.yaml

@@ -13,7 +13,7 @@ jobs:
       - uses: actions/checkout@v2
       - uses: actions/setup-node@v3
         with:
-          node-version: 16.x
+          node-version: 18.x
 
       - name: Add key to allow access to repository
         env:

.github/workflows/testing.yaml

@@ -13,7 +13,7 @@ jobs:
       - uses: actions/checkout@v2
       - uses: actions/setup-node@v3
         with:
-          node-version: 16.x
+          node-version: 18.x
 
       - name: Install dependencies
         run: npm ci

docs/terranetes-controller/admin/providers.md

@@ -211,7 +211,7 @@ spec:
 :::caution
 Details on binding can be found [here](https://azure.github.io/aad-pod-identity/docs/concepts/azureidentitybinding/), but essentially it's used to filter the pods in the namespace and provide the permissions to the pods that match the labels - i.e. the pod must have label of the same name and value.
 
-As of <= v0.3.30 the pod selector is not configurable in the controller to ensure you use `terranetes-executor` on the binding.
+As of \<= v0.3.30 the pod selector is not configurable in the controller to ensure you use `terranetes-executor` on the binding.
 :::
 
 #### Service Account Permissions

docs/terranetes-controller/cli/tnctl_completion_bash.md

@@ -14,7 +14,7 @@ If it is not installed already, you can install it via your OS's package manager
 
 To load completions in your current shell session:
 
-	source <(tnctl completion bash)
+	source \<(tnctl completion bash)
 
 To load completions for every new session, execute once:
 

docs/terranetes-controller/cli/tnctl_completion_zsh.md

@@ -16,13 +16,13 @@ to enable it.  You can execute the following once:
 
 To load completions in your current shell session:
 
-	source <(tnctl completion zsh)
+	source \<(tnctl completion zsh)
 
 To load completions for every new session, execute once:
 
 #### Linux:
 
-	tnctl completion zsh > "${fpath[1]}/_tnctl"
+	tnctl completion zsh > "$\{fpath[1]}/_tnctl"
 
 #### macOS:
 

docs/terranetes-controller/cli/tnctl_create_workflow.md

@@ -22,7 +22,7 @@ Generate a workflow for module
 $ tnctl create workflow PATH
 
 You can override the location of the template via the configuration
-file ${HOME}/.tnctl/config.yaml (or TNCTL_CONFIG). Just add the
+file $\{HOME}/.tnctl/config.yaml (or TNCTL_CONFIG). Just add the
 following
 
 ---

docs/terranetes-controller/cli/tnctl_kubectl_plugin.md

@@ -14,11 +14,11 @@ called from kubectl. You need to ensure the scripts this command
 generates are included your $PATH, long with the location of the
 tnctl command.
 
-Create the kubectl plugins (defaults to ${HOME}/bin)
+Create the kubectl plugins (defaults to $\{HOME}/bin)
 $ tnctl kubectl plugin
 
 Place the plugins scripts in another directory
-$ tnctl kubectl plugin -d ${GOPATH}/bin
+$ tnctl kubectl plugin -d $\{GOPATH}/bin
 
 
 ```

docs/terranetes-controller/cli/tnctl_workflow_create.md

@@ -16,7 +16,7 @@ Generate a workflow for module
 $ tnctl workflow create PATH
 
 You can override the location of the template via the configuration
-file ${HOME}/.tnctl/config.yaml (or TNCTL_CONFIG). Just add the
+file $\{HOME}/.tnctl/config.yaml (or TNCTL_CONFIG). Just add the
 following
 
 ---

docs/terranetes-controller/developer/private.md

@@ -14,7 +14,7 @@ Let's assume we have a terraform module hosted in a private Github repository. H
 2. Create a Kubernetes secret in the namespace containing the SSH private key.
 
     ```shell
-    $ kubectl -n apps create secret generic ssh --from-file=SSH_KEY_AUTH=id.rsa
+    $ kubectl -n apps create secret generic ssh --from-file=SSH_AUTH_KEY=id.rsa
     ```
 
 3. Update the Terraform module configuration resource, setting the `spec.auth.name: [NAME]` to the name of the secret: