-
### Expected Behavior
S3 secrets should both contain the same contents.
### Current Behavior
```
kubectl describe secret localega-s3-keys -n lega
Name: localega-s3-keys
Namespace: …
-
#### Description
In order to facilitate deployment of LocalEGA Data-In we are planning to add the helm option of deployment.
Configuration should be generated on disk and loaded into helm charts…
-
### Expected Behavior
cega-mq should successfully mount the necessary volumes and start accordingly
### Current Behavior
```
lega-se-testy-service-000 MountVolume.SetUp failed for volume "te…
-
### Expected Behavior
Users are unable to login to inbox because the ega_ssh_keys binary is segfaulting during operation.
### Current Behavior
```
[root@lega-localega-inbox-66f95f4f45-vt9ks eg…
-
### Description
All communication between our services needs to be TLS terminated, including the cluster internal communication. As a result we can not rely on external PKI providers and thus must …
-
**Issue by [blankdots](https://github.com/blankdots)**
_Thursday Sep 06, 2018 at 11:39 GMT_
_Originally opened as https://github.com/NBISweden/LocalEGA/issues/343_
----
Since https://github.com/NBI…
-
### Description
We would like add an end to end testing as part of the deployment that tests:
1. Encrypts a file
2. Encrypted file can be ingested
3. Mocks the `stable_id` generation
4. Mocks the…
-
### Description
RES microservice should support storage backends with Cleversafe, S3 and POSIX interfaces. In the past it was possible to specify which storage backend is suppose to be used in conf…
-
### Expected Behavior
`ingest` and `verify` microservices should be able to talk to S3 over `https`.
### Current Behavior
Currently, if S3 backend (Minio in our case) is TLS-enabled, `ingest` and…
-
### Description
Currently the easiest way of deploying a Kubernetes cluster for Local-EGA is by using `kubenow`, a tool that is likely to no longer be maintained. The provided solution, based on T…