Use a fork of the k3s dagger module that adds:
- Optional debug parameter (defaults to false) to disable k3s server debug logs
- Optional kubeletVerbosity parameter (defaults to 1) for kubelet log control
This eliminates verbose output from both k3s server (certificate generation,
database init) and kubelet (container operations, volume cleanup) while
maintaining visibility of errors and warnings.
Kubelet verbosity is controlled via a configuration file placed in the k3s
config directory before kubelet initializes, avoiding the logging configuration
immutability issue.
Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
The latest version v0.1.10 fix the issue #297 that was producing that
the CI failed every time because of the cache didn't exists and needed
to wait for the server to start.
Closes#297
Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
Rework the e2e test to expect a working connection to a cluster when
they start. Developers can create their own clusters and run the tests.
Removed the code used to start kind clusters within the e2e tests.
Reworked the Taskfile to define two environments where the tests can run:
1. An ephemeral one running within Dagger, using the k3s module, to be
used by the CI.
2. A persistent one created with Kind, requiring the kind binary, to be
used for development and debugging when the ephemeral cluster is not
enough.
Signed-off-by: Francesco Canovai <francesco.canovai@enterprisedb.com>
Signed-off-by: Leonardo Cecchi <leonardo.cecchi@enterprisedb.com>
Co-authored-by: Leonardo Cecchi <leonardo.cecchi@enterprisedb.com>
