Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

incorrect workload names in flux #2011

Closed
jan-schumacher opened this issue May 3, 2019 · 1 comment · Fixed by #2018
Closed

incorrect workload names in flux #2011

jan-schumacher opened this issue May 3, 2019 · 1 comment · Fixed by #2018
Assignees
Labels

Comments

@jan-schumacher
Copy link

jan-schumacher commented May 3, 2019

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.

default:helmrelease/redis                     application
default:helmrelease/redis                     application
default:helmrelease/redis                     application
default:helmrelease/redis                     application
default:helmrelease/redis                     application
default:helmrelease/redis                     application
default:helmrelease/redis                     chart-image

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.

---
apiVersion: flux.weave.works/v1beta1
kind: HelmRelease
metadata:
  name: some-app
  namespace: default
  annotations:
    flux.weave.works/automated: "true"
    flux.weave.works/tag.chart-image: glob:master-*
spec:
  releaseName: some-app
  chart:
    git: [email protected]:/repository/repo.git
    path: charts/some-chart
    ref: master
  values:
    application:
      image: eu.gcr.io/project-name/some-app:master-123
    other:
      settings: {}

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. create 2 helmReleases
    1.1. Call one faulty the other faulty2
    1.2. Add them to the repository
    1.3. Do $ fluxctl sync
  2. Do $ fluxctl list-workloads | grep helmrelease

Error
The output of $ fluxctl list-workloads | grep helmrelease

default:helmrelease/faulty2                                                                          
default:helmrelease/faulty2

Expected behavior
The workload names should match the release names. $ fluxctl list-workloads | grep helmrelease should produce something like

default:helmrelease/faulty                                                                         
default:helmrelease/faulty2
@hiddeco hiddeco added the bug label May 3, 2019
@2opremio 2opremio added the blocked-needs-validation Issue is waiting to be validated before we can proceed label May 7, 2019
@2opremio 2opremio added this to the v1.12.2 milestone May 7, 2019
@2opremio 2opremio self-assigned this May 7, 2019
@2opremio 2opremio removed the blocked-needs-validation Issue is waiting to be validated before we can proceed label May 7, 2019
@hiddeco hiddeco removed this from the v1.12.2 milestone May 7, 2019
@jan-schumacher
Copy link
Author

Nice! Thanks alot! Just updated and it's working just fine.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants