-
**What happened**:
1. Deployed **litmus** Helm chart v3.9.0 on a private GKE cluster in the litmus-operator namespace via ArgoCD.
2. The control plane components are working fine and I can access…
-
### Describe the bug
When applying an helm chart from an oci repository, chart version appended with a suffix leading to edge cases on some charts.
### Steps to reproduce
Given this :
```yaml
a…
-
Setting up a teleport in EKS cluster 1.30 with helm was somewhat easy. I created dynamodb tables for events and config, S3 bucket, IAM role, added this to Access Entry (Pod identity over IRSA, since t…
-
In my dashboard component, I used ApexCharts. The project compiles fine without any errors, but the chart does not render on the front end.
**HTML code**
```
…
-
### Describe the bug
We deployed the flyte-binary chart and are having problems mounting secrets from k8s secrets.
This is the workflow:
```python
secret = Secret(
group="dotfile-secret"…
-
This happens with every release. I wanted to post here to see if there is anything we can do before we spend the time reverting.
Process
1. We Install Helm Charts with Terraform.
2. We genera…
-
### Name and Version
bitnami/keycloak 23.0.0
### What is the problem this feature will solve?
The problem I am trying to solve is the fact that we cannot activate OTP MFA for the admin Keycloak acc…
-
## Context:
Helm chart version: 2.18.1
We are using skaffold and kustomize to build and deploy uptime-kuma to our GKE cluster in our GCP project. Normal flow is verify that the manifest is properl…
-
### Name and Version
bitnami/elasticsearch 21.3.21
### What architecture are you using?
None
### What steps will reproduce the bug?
1. Create a project with a dot `.` in name. e.g. `elasticsearch…
-
Initially I was only thinking about Nexus requiring a port per image registry. But since we are supporting Nexus pro, we should be able to set this up via subdomain routing that Nexus supports for the…