Long running k8s models don't have the same labels applied to pods as new models

Bug #2017240 reported by Tom Haddon
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju

Bug Description

We have a k8s model (now running 2.9.42) that's been running for 617 days (I don't know the exact version it was originally deployed on, let me know if there's a way to look that up), and have done a switch from pod-spec charms to sidecar charms. As part of doing this, we noticed the pods have a label of `juju-app=wordpress-k8s` rather than `app.kubernetes.io/name=wordpress-k8s` which seems to be applied if you deploy from scratch using the same version of Juju (2.9.42 in both cases).

This is causing problems for some applications that are depending on a label we're expecting to be there.

Tags: canonical-is
Tom Haddon (mthaddon)
tags: added: canonical-is
Revision history for this message
Harry Pidcock (hpidcock) wrote :

Legacy labels are model specific, we won't fix this in 2.9, but in future versions we could maintain both sets of labels for old models.

Changed in juju:
importance: Undecided → High
milestone: none → 3.3.0
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.