You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
the container application is obvious, because all image keys are under application key. Thats correct.
But depending on what deploys last the workload is named default:helmrelease/redis. When I delete redis the workload is default:helmrelease/fluxcloud.
After some researches and testing I figured out that all helm releases are named the same in flux and I can’t figure out why.
the container
application
is obvious, because all image keys are under application key. Thats correct.But depending on what deploys last the workload is named
default:helmrelease/redis
. When I delete redis the workload isdefault:helmrelease/fluxcloud
.This is how a typical helm release looks like in our case. Any ideas what is wrong or did I find a bug in flux? (edited)
**Setup: **
Kubernetes 1.12.7-gke.10
Helm v2.12.2
flux 1.12.1
fluxctl 1.12.0
flux-helm-operator 0.8.0
Reproduce:
1.1. Call one faulty the other faulty2
1.2. Add them to the repository
1.3. Do
$ fluxctl sync
$ fluxctl list-workloads | grep helmrelease
Error
The output of
$ fluxctl list-workloads | grep helmrelease
Expected behavior
The workload names should match the release names.
$ fluxctl list-workloads | grep helmrelease
should produce something likeThe text was updated successfully, but these errors were encountered: