Juju is not labeling all the Kubernetes Resources created by a charm

Bug #1949103 reported by Dominik Fleischmann
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju

Bug Description

There are several cases where juju is not labeling Kubernetes Resources that are created by a charm:

== 1.==
Resources that are deployed by workloads that are deployed from charms. For Example, the Jupyter Notebook Controller is deployed through charms will deploy Notebook Servers in different namespaces which will not contain juju labels. Steps to reproduce:

# Bootstrapped on microk8s with storage DNS, ingress and metallb: enabled

# Deploy the kubeflow-lite bundle following these instructions: https://charmed-kubeflow.io/docs/install

# Create a Notebook Server like described in the "Creating a Kubeflow Notebook" section here: https://charmed-kubeflow.io/docs/kubeflow-basics

# Check labels of the "test" notebook server pod:
microk8s kubectl -n admin get pod/test-0 -o yaml

== 2.==
When creating resources through kubectl or istioctl. This is a pattern used in the istio sidecar charm. It does not happen when creating resources through a python library like lightkube. This can be reproduced the following way:

# Bootstrapped on microk8s with storage DNS and ingress enabled

juju deploy ch:istio-gateway istio-ingressgateway-operator --config=kind=ingress --trust
juju deploy istio-pilot --trust
juju relate istio-pilot istio-ingressgateway-operator

# Describing the istio-ingressgateway pod (not the one for pebble) it will not have any labels.
microk8s kubectl -n istio get pod/istio-ingressgateway -o yaml

description: updated
Harry Pidcock (hpidcock)
Changed in juju:
importance: Undecided → Medium
milestone: none → 3.2-beta1
status: New → Triaged
Changed in juju:
milestone: 3.2-beta1 → 3.2-rc1
Changed in juju:
milestone: 3.2-rc1 → 3.2.0
Changed in juju:
milestone: 3.2.0 → 3.2.1
Changed in juju:
milestone: 3.2.1 → 3.2.2
Changed in juju:
milestone: 3.2.2 → 3.2.3
Changed in juju:
milestone: 3.2.3 → 3.2.4
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.