-
## Description
Currently, if a release is created, we must manually build and push the "app dev container base" under `tools/app_dev_container_base`.
To make things easier, we shall build and …
-
## Description
Currently as implemented in #5 existing containers in status "exited" will be deleted and re-created on device restart. Measurements have revealed that the creation of a container bu…
-
## Description
The idea is to provide a command line command like `npm init` or `cargo init` to create a new ready to use Ankaios workload development project setup based on our workload examples …
-
## Description
What a `running` workload means is a matter of interpretation and is very specific to the use-case and the workload.
For some use-cases a basic `container is running` is enough (cur…
-
Reported by @lingnoi:
## Description
Currently the communication between agent/cli and server is done using the API definition in **ankaios.proto**. The same is used for the communication throug…
-
## Description
Currently we are facing issues with maintaining different custom error types and conversions between them.
It would be great to follow the principle to have module group-wide errors…
-
## Description
Currently we are using plain strings for the agent and workload names and for the runtime. To improve the readability and reduce the chance for mistakes, we can add dedicated types.
…
-
## Description
Pre-built binaries `ank` CLI would be nice to have for MacOS and Windows as well.
Maybe we can extend the release by providing binaries for x86_64 and arm64 Silicon.
## Goals
…
-
## Description
The basic idea here is to skip the creation of the control interface if the configuration of the workload does not contain a control interface field. Doing this will spare some green…
-
## Current Behavior
If one of the resources in the `manifest` part of a podman-kube workload is invalid,
this can lead to `podman kube play` and `podman kube down` to fail.
As during the creation…