# Connect to Kubernetes targets without specifying a target group

## `zli v. 6.28.0`

### Enhancements

* **Connect to Kubernetes targets without specifying a target group.** When connecting to a Kubernetes target, if the associated policy has only 1 configured target group, then you do not need to specify it in your `connect` command. Similarly, if there is only 1 target user configured, your connect command may look like `zli connect my-kubernetes-target`

## `bzero v. 8.0.4`

### Fixes

* **Web daemon and query parameters.** This release contains the daemon code needed to support the query parameter fix for web daemons that was released on [08/01/23](https://changes.bastionzero.com/2023/pages/Yo82eH2YWITwjjYIujG7#zli-v.-6.27.4). To consume this fix, upgrade your `zli` to `6.27.4`. There is no action needed for agents

## Web app & backend

### Enhancements

* **Connect to Kubernetes targets without specifying a target group.**  This release of the backend contains the changes necessary to support connecting to Kubernetes targets with a default target group

### Fixes

* **Connect to a target that shares its name with other target(s).** Resolved an issue where target connect does not always choose the online target when multiple targets with the same name exist in different states

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-kubernetes-targets-without-specifying-a-target-group.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.