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
When following the steps in the above mentioned documentation page, linkerd and linkerd-viz namespace has to be created manually. In that case it is created without any labels or annotations, at least when linkerd is installed using helm. Please, update a snipped so that users know how to properly label and annotate the namespaces, e.g.:
# control plane core
kubectl create namespace linkerd
kubectl label namespace linkerd linkerd.io/is-control-plane=true \
config.linkerd.io/admission-webhooks=disabled \
linkerd.io/control-plane-ns=linkerd
kubectl annotate namespace linkerd linkerd.io/inject=disabled
# viz (ignore if not using the viz extension)
kubectl create namespace linkerd-viz
kubectl label namespace linkerd-viz linkerd.io/extension=viz
kubectl annotate namespace linkerd-viz config.linkerd.io/proxy-await=enabled linkerd.io/inject=enabled
# viz (ignore if not using the jaeger extension)
kubectl create namespace linkerd-jaeger
I do not know what labels and/or annotations are needed for jaeger extension.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When following the steps in the above mentioned documentation page,
linkerd
andlinkerd-viz
namespace has to be created manually. In that case it is created without any labels or annotations, at least when linkerd is installed usinghelm
. Please, update a snipped so that users know how to properly label and annotate the namespaces, e.g.:I do not know what labels and/or annotations are needed for jaeger extension.
Beta Was this translation helpful? Give feedback.
All reactions