Welcome to the Simpl-Open Installation Forum, the dedicated space to discuss the deployment of the Simpl-Open agents. Whether you're encountering specific issues or need clarification, share them here!
For detailed step-by-step instructions, please refer to our Installation Guide and User Manual.
Hello,
I am following the installation guide that was used for the workshop of the agents, specifically the version v1.3.2 of the common components, and I have a couple of questions regarding the prerequisites.
In the documentation, cert-manager is listed as a prerequisite, and the .yaml for deployment in ArgoCD references a ClusterIssuer named dev-prod by default. However, there is no information on what configuration is expected.
I have tested both selfSigned and internal CA setups (with a root CA managed by cert-manager), but in both cases the Vault Agent Injector does not trust the CA, and the pods fail to become ready (stuck in Init:1/2 or CrashLoopBackOff).
Thank you in advance for clarifying these points.
Hello,
We are encountering, the same, recurring issues where one of the initialization pod, most frequently the vault-init container, fails with the following error:
tls: failed to verify certificate: x509: certificate signed by unknown authority
Hello Pablo Arquellada Cebrián & Nick Vermeulen,
Thank you for reaching out and welcome to our community! Our team will review your request and respond with the next steps within 15 working days.
We appreciate your comments and encourage you to participate in our forums.
Hello team,
During the installation of Simpl-Open, in the Common-Components v1.3.2 agent the pod redis-master-0 started failing with the following error:
Failed to pull image "docker.io/bitnami/redis:7.2.5-debian-12-r0": rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/bitnami/redis:7.2.5-debian-12-r0": failed to resolve reference "docker.io/bitnami/redis:7.2.5-debian-12-r0": docker.io/bitnami/redis:7.2.5-debian-12-r0: not found
After investigating, I noticed that Bitnami announced a migration of their images to a new repository (bitnamilegacy) on Docker Hub. At this point, the image bitnami/redis:7.2.5-debian-12-r0 is no longer available under bitnami/redis, which causes the deployment to fail.
Could you please confirm whether Simpl-Open should be updated to use a newer tag or if it should reference the bitnamilegacy repository instead?
Looking forward to your guidance so I can proceed with the installation.
Best regards,
Dear Nick & Pablo,
First and foremost, we would like to sincerely thank you for your valuable contributions and engagement on this forum. Your efforts in identifying and discussing issues related to the Simpl-Open installation are greatly appreciated and help us improve the programme for everyone.
Regarding the issues you've reported, we'd like to provide some clarification and guidance.
Pablo, you've encountered an issue with the Redis image pull failure, where the pod redis-master-0 failed with an error indicating that the image "docker.io/bitnami/redis:7.2.5-debian-12-r0" was not found. This is because Bitnami has migrated their images to a new repository (bitnamilegacy) on Docker Hub. To resolve this issue, you can update the image reference in the ArgoCD pod manifest to "docker.io/bitnamilegacy/redis:8.2.1-debian-12-r0", as you've already done. We are busy internally with a hotfix for this as well.
Nick, you've reported an issue with certificate verification, where the Vault Agent Injector does not trust the CA, and the pods fail to become ready. This is because the certificate needs to be a trusted one, such as one issued by a publicly trusted CA like Let's Encrypt. Using a self-signed certificate or an internal CA may not work, as the cert-manager may not be able to verify the certificate chain. To resolve this issue, we recommend using a trusted CA, and configuring the ClusterIssuer accordingly. We will provide more detailed guidance on this in our documentation, which will be updated soon.
To ensure that technical issues are handled efficiently and transparently, we encourage all community members to use GitLab for reporting technical issues. This helps us maintain a structured and collaborative approach to problem-solving.
GitLab Issue: Issues · Simpl · GitLab
For general information on how to participate and contribute to the Simpl Programme, you can visit our official page: How to participate | Simpl Programme
Thank you once again for your support and dedication to the Simpl Programme.
Kind regards,
Rick on behalf of The Simpl Programme Team
Hello Rick,
The Bitnami issue should now be fixed, since the image you are using is available again on bitnami/redis.
Thanks, however!
Best regards,
Hello,
I would like to know who is trying to install or successfully installed SIMPL. I am willing to organise some sort of workgroup to discuss and share info on deploying/customising it.
Just reply to this message and I'll contact you later.
Cheers!
Thank you for this, Carlos.
It sounds like an excellent idea!
Please let me know how we can help.
We also have these guides and videos available:
Installation guide.
User manual.
Installation video.
Bear in mind that one has to be logged in to access the installation videos.
Hello. In Luxembourg National Data Service are also exploring the installation of Simpl-Open for Genomic Data Infrastructure and ICUData4EU.
Given our available computing and human resources, we may not be able to install Simpl Open ArgoCD and Kubernetes. Beyond that, we already have technologies in place, so full-blown replacement of existing stack is not feasible anyways.
We are currently working on digesting all the helm charts, to identify which capabilities we could already reuse to fill the gaps in these proejcts.
Dear Bruno,
Thank you for your question.
At present, the SIMPL-Open installation documentation is written for deployments based on ArgoCD and Kubernetes. As a result, the installation guides, examples, and deployment procedures assume that these technologies are being used.
That said, SIMPL-Open itself is not inherently limited to ArgoCD and Kubernetes. The software can be deployed in other environments, and it is possible to reuse individual components and capabilities within an existing technology stack.
In summary, the current limitation is not the software itself but the scope of the available installation documentation, which assumes an ArgoCD and Kubernetes-based deployment model.
Kind regards,
Simpl community team
Hello,
Trying to onboard and integrate Simpl-Open into Common European Energy Data Space (CEEDS) - INSIEME project. It is not clear how to proceed with the customization of configuration and installation since we need to integrate existing solutions and to develop specific layers for Simpl-Open.
Creating a basic instance requires considerable amount of resources and it is not possible to strip down the installation to use only some components.
We need help from Simpl-Open community and support for further adoption.
Thank you in advance.
Dear Dragos-Constantin,
Thank you for your message and for your interest in adopting Simpl-Open within the CEEDS-INSIEME project.
We understand the challenges associated with integrating SIMPL-Open into an existing technical environment, particularly when only a subset of its capabilities is required and existing solutions are already in place.
At present, Simpl-Open supports deployment through the installation mechanisms documented by the project, and the available installation guidance is focused on the deployment of the full solution stack. We are not yet in a position to provide documentation or guidance for deploying only selected components or agents independently.
As part of our ongoing work, we are preparing additional installation guidance for specific services, including the Catalogue Service, together with the required dependencies.
However, the integration of these components into an existing environment, the customization of deployments, and the reuse of available organisational infrastructure remain implementation choices that need to be assessed and carried out by the adopting organization. At this stage, we do not provide detailed guidance on how to integrate individual Simpl-Open services into third-party architectures or existing technology stacks.
As additional installation documentation becomes available, it will be shared with the community.
Kind regards,
Simpl community team
Dear Lotte,
Thank you for your message.
Looking forward for the documentation and further development of Simpl/SIMPL-Open project.
Kind regards,
Dragoș
Hello team,
As a temporary workaround, I manually changed the image in the ArgoCD pod manifest to:
image: docker.io/bitnamilegacy/redis:8.2.1-debian-12-r0
With this change, the pod started correctly, so the issue is resolved locally, until sync operation is done. However, this fix needs to be applied in the source repository so that deployments work out of the box without manual intervention.
Could you please update the repo to use the new image reference?
Thanks in advance,