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
Currently if helm release/instance is named same as the chart, coredns, it keeps that duplicate string in the fullname template.
So all objects created by this chart have not that smart naming.
The standard is to not include the release name string in the fullname template.
Current object names, when helm release is named coredns:
kubectl -n kube-system get all,sa,clusterrole,clusterrolebinding,smon -l app.kubernetes.io/instance=coredns
NAME READY STATUS RESTARTS AGE
pod/coredns-coredns-6db9976d78-drpdc 1/1 Running 1 (11h ago) 15h
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/coredns-coredns-metrics ClusterIP 10.30.232.118 <none> 9153/TCP 15h
service/kube-dns ClusterIP 10.30.0.10 <none> 53/UDP,53/TCP 15h
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/coredns-coredns 1/1 1 1 15h
NAME DESIRED CURRENT READY AGE
replicaset.apps/coredns-coredns-6db9976d78 1 1 1 15h
NAME SECRETS AGE
serviceaccount/coredns-coredns 0 15h
NAME CREATED AT
clusterrole.rbac.authorization.k8s.io/coredns-coredns 2023-12-27T13:55:55Z
NAME ROLE AGE
clusterrolebinding.rbac.authorization.k8s.io/coredns-coredns ClusterRole/coredns-coredns 15h
NAME AGE
servicemonitor.monitoring.coreos.com/coredns-coredns 15h
You can see that coredns-coredns is everywhere.
The text was updated successfully, but these errors were encountered:
Currently if helm release/instance is named same as the chart,
coredns
, it keeps that duplicate string in thefullname
template.So all objects created by this chart have not that smart naming.
The standard is to not include the release name string in the
fullname
template.Current object names, when helm release is named
coredns
:You can see that
coredns-coredns
is everywhere.The text was updated successfully, but these errors were encountered: