agent icon indicating copy to clipboard operation
agent copied to clipboard

Stackable Agent - a kubelet written in Rust which uses systemd as its backend

Results 51 agent issues
Sort by recently updated
recently updated
newest added

The package for Debian is signed but the ones for CentOS are not. They should be signed and the documentation should be adapted (i.e. `gpgcheck=0` should be removed, see #294).

type/enhancement

The agent currently does not honor the HTTP_PROXY environment variable and offers no command line parameters to configure a proxy either. For the connection to Kubernetes a proxy is not...

type/enhancement
good first issue
priority/low
status/blocked

During the early life of the agent some decisions on code structure were not taken the way that they maybe shoud have taken. This makes the code less testable and...

type/enhancement
priority/high
Epic

> Conversion from `prost_types::Timestamp` to `SystemTime` can cause an overflow and panic | Details | | | ------------------- | ---------------------------------------------- | | Package | `prost-types` | | Version | `0.7.0`...

priority/medium
status/blocked
type/security

Currently the agent relies on system provided openssl libraries for all TLS concerns. We could potentially switch to using rustls [1] which would remove our dependency on ssl system libraries...

priority/medium
status/blocked
type/question

We need to define, which pod properties we initially want to support and how we want to map those to our systemd unit files. I'll just start with my initial...

type/documentation
priority/medium

Currently, if a user provides a tag/label with a comma that'll break our agent un unpredictable ways. One solution, for now, is to simply disallow such labels.

type/bug
priority/medium

Kubectl logs has a flag which allows retrieving the logs for an earlier iteration of a pod. We should also support this and retrieve logs from the previous systemd service...

type/enhancement
priority/low
status/blocked

Currently the agent does not expose anything on its internal state, or errors that occurred during execution. We should start adding the ability to set node conditions [1] for anything...

type/enhancement
priority/medium