ron1
ron1
**Describe the solution you'd like** GitLab Provider support for GitLab Group-level CI/CD Variables. Currently, only GitLab Project-level CI/CD Variables are supported. **What is the added value?** The ESO GitLab Provider...
## Overview Function [initialize.RestrictedSecurityContext()](https://github.com/CrunchyData/postgres-operator/blob/8b14582aaa9df139b8eb38fe48a47f546db61f02/internal/initialize/security.go#L34) must set securityContext.seccompProfile in order to satisfy PSS Restricted Profile. This is not currently the case. ## Environment Please provide the following details: - Platform: (`Rancher...
Opni should manage the TLS certs required to securely connect Alertmanager to custom webhook receivers. Opni could simplify this management via some cert-manager/alertmanager automation. It would be great if a...
The Logging Backend v0.11.1 uninstall should tolerate various types of failed installs. I was unable to uninstall a failed install from the web ui. Rather, I had to use kubectl...
A common GitOps practice is to create and manage Secrets outside of package managers like Helm and Kustomize. The opni-agent helm values file currently does not support this practice since...
### What problem are you facing? Some environments rely on gith ssh based auth for private repositories instead of the currently supported token one. The Upbound provider-terraform shares this problem...
**Is your feature request related to a problem? Please describe.** Update loki helm chart to depend on alloy not grafana-agent-operator. The grafana-agent-operator is deprecated. **Describe the solution you'd like** Loki...
**Describe the bug** PushSecret fails to push `.spec.template.metadata`. **To Reproduce** Steps to reproduce the behavior: With ESO v0.9.13 installed on kubernetes 1.26.5, add an annotation and label to the sample...
### Is your feature request related to a problem? Please describe. I am unable to use an existing secret generated by a Secrets Manager such as the external-secret operator for...
**Describe the problem/challenge you have** I need to rename secret when importing it into a new namespace. **Describe the solution you'd like** Add field SecretRequest.spec.fromName which allows SecretRequest.name and SecretRequest.spec.fromName...