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 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,