Benjamin Alpert

Document DynamoDB compatible backend for non-AWS Teleport clusters

2

**What happened**: DynamoDB is currently limited to AWS instances only. This reduces the capability to deploy Teleport in non-AWS related environments. Noteworthy projects are: - https://github.com/dwmkerr/docker-dynamodb - https://github.com/scylladb/scylla -> https://www.scylladb.com/2019/09/11/scylla-alternator-the-open-source-dynamodb-compatible-api/...

Expose human-understandable cluster operations status via CRD status field

3

Operator Version: 2.1.1 Opensearch Version 1.3.6 (cannot update due to software dependency) When I am creating an `opensearchCluster` the pods are deployed and the cluster is available after some time....

Option to support virtual text wrapping of symbol details

1

I am currently configuring outline for my setup. With `opts = { outline_window = { wrap = true }, outline_items = { show_symbol_details = true } }` the wrapping only...

# Summary Similar to https://github.com/ironcore-dev/ironcore/issues/1114 the same `Reclaim Policy` should be available for `Virtual IP` resources. ## Basic example ``` apiVersion: compute.ironcore.dev/v1alpha1 kind: Machine metadata: name: machine spec: networkInterfaces: -...

# Summary A `NetworkInterface` exposes the possibility to configure either a predefined `Virtual IP`resource or have it ephemerally managed by a template configuration (see https://github.com/ironcore-dev/ironcore/blob/main/api/networking/v1alpha1/networkinterface_types.go#L50-L56). Other `Networking` resources such as...

# Summary When creating a `Machine` resource there is the possibility to create the resource with an ephemerally managed `Volume` resource. The resulting `Volume` will show an `ownerReference` entry pointing...

### Feature Description Hi, thanks for this awesome work. My use case is the following: when accepting an item from the completion list, based on the key I have used...

partially fixes #1282

# Summary Compared to the `machine` status (https://github.com/ironcore-dev/ironcore/blob/main/api/compute/v1alpha1/machine_types.go#L176) the `volume` and `bucket` status struct is missing such a field. We would like to consistently implement the possibility to let either...

variables for `go build` need to be passed on to `docker-build` recipes. Following up for [a suggestion in PR introducing variables which are meant to be set at build time](https://gitlab.devops.telekom.de/cas-devs/osc/upstream/release-ironcore/-/jobs/244030390#L721)....