Hi, running into trouble with the Fleet v0.8.0 release. Consider the following fleet.yaml

defaultNamespace: ns-test2
namespaceLabels:
  foo: barLabel
  <http://pod-security.kubernetes.io/enforce|pod-security.kubernetes.io/enforce>: restricted
  <http://pod-security.kubernetes.io/enforce-version|pod-security.kubernetes.io/enforce-version>: latest
namespaceAnnotations:
  foo: barAnnotation
kustomize:
  dir: overlays

and then the following:

#overlays/kustomization.yaml

resources:
- ./secret.yaml
- ./namespace.yaml

and

#overlays/namespace.yaml

apiVersion: v1
kind: Namespace
metadata:
  labels:
    <http://pod-security.kubernetes.io/enforce|pod-security.kubernetes.io/enforce>: restricted
    <http://pod-security.kubernetes.io/enforce-version|pod-security.kubernetes.io/enforce-version>: latest
  name: ns-test2

and

#overlays/secret.yaml

apiVersion: v1
kind: Secret
metadata:
  name: dotfile-secret
data:
  .secret-file: dmFsdWUtMg0KDQo=

I would expect to see the namespace

ns-test2

to get created with the pss labels, but they aren't. Instead I get the following error:

Unable to continue with install: Namespace "ns-test2" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "<http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>": must be set to "Helm"; annotation validation error: missing key "<http://meta.helm.sh/release-name|meta.helm.sh/release-name>": must be set to "something"; annotation validation error: missing key "<http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>": must be set to "ns-test2"]; namespace.v1 ns-test2 missing

Note I redacted it a bit