# Connect to all Kubernetes targets in a single command

## `zli v. 6.33.4`

### New

* **Connect to all Kubernetes targets in a single command.** Beginning with `zli v. 6.33.4`, `zli connect -t kubernetes` will prompt the `zli` to open a connection to every Kubernetes target you can access according to your organization's policies. For each target, a unique connection is opened for every available target user. Switch between connections by updating your current Kube context

### Fixes

* **Connect to a virtual target by ID.** Resolved an issue preventing users from connecting to a web or database target by ID
* **`zli target list` results.** Resolved an issue with `zli target list` returning duplicate results if a user has access to a single target via JIT access and standard policy

***

## `bzero v. 8.0.7`&#x20;

### New

* **AWS RDS MySQL support.** `bzero v. 8.0.7` contains support for securing passwordless access to RDS MySQL targets. To get started, reach out to <product@bastionzero.com>

### Enhancements

* **Windows agent.** For consistency among the agents, the Windows agent is now `bzero-agent.exe` (formerly `agent.exe`)

***

## Web app & backend

### Fixes

* **JIT targets.** Resolved an issue where some JIT-accessible targets returned incorrect target users
* **Connect to a Kubernetes target.** Resolved an issue with connecting to a Kubernetes target when allowed target groups have a conflict with a given target user

For questions or to provide feedback on how we can improve our updates, reach out to [<mark style="color:purple;">product@bastionzero.com</mark>](mailto:product@bastionzero.com).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://changes.bastionzero.com/2023/connect-to-all-kubernetes-targets-in-a-single-command.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
