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
{{ message }}
This repository has been archived by the owner on Feb 27, 2024. It is now read-only.
I would like to suggest that nxrm-aws-resiliency stop managing the namespace nexusrepo. The side effect of the nxrm chart managing the namespace is that the helm release and the nexus-nxrm-aws-resiliency pod are in separate namespaces.
$ helm ls -n defaultNAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSIONnexus default 5 2023-11-03 17:19:07.787659544 -0400 EDT deployed nxrm-aws-resiliency-61.1.0 3.61.0
$ kubectl --namespace default -l app=nxrm get poNo resources found in default namespace.
$ kubectl --namespace nexusrepo -l app=nxrm get poNAME READY STATUS RESTARTS AGEnexus-nxrm-aws-resiliency-54d698879b-6fk6t 4/4 Running 6 (24m ago) 29m
If these lines were removed, kubernetes admins could install the helm release and kubernetes resources in any namespace... and they'd be colocated in the same namespace. Which will help cut down on confusion.
The text was updated successfully, but these errors were encountered:
I would like to suggest that nxrm-aws-resiliency stop managing the namespace
nexusrepo
. The side effect of the nxrm chart managing the namespace is that the helm release and the nexus-nxrm-aws-resiliency pod are in separate namespaces.If these lines were removed, kubernetes admins could install the helm release and kubernetes resources in any namespace... and they'd be colocated in the same namespace. Which will help cut down on confusion.
The text was updated successfully, but these errors were encountered: