The namespace-configuration-operator helps keeping configurations related to Users, Groups and Namespaces aligned with one of more policies specified as a CRs
Apache License 2.0
204
stars
55
forks
source link
reconcile error triggered by some status fields to be set to invalid values #49
Version 0.2.0 complains about setting some setting some status fields of the CR to invalid values on namespace creation, but keeps working. It logs the below error (human readable form here, raw details are below):
error:
NamespaceConfig.redhatcop.redhat.io "networkpolicy-isolate-namespaces" is invalid:
[
status.lockedResourceStatuses.networking.k8s.io/v1/NetworkPolicy/test1/allow-from-same-namespace: Invalid value: "null":
status.lockedResourceStatuses.networking.k8s.io/v1/NetworkPolicy/test1/allow-from-same-namespace in body must be of type array: "null",
status.lockedResourceStatuses.networking.k8s.io/v1/NetworkPolicy/test1/allow-from-system-namespaces: Invalid value: "null":
status.lockedResourceStatuses.networking.k8s.io/v1/NetworkPolicy/test1/allow-from-system-namespaces in body must be of type array: "null"
]
Version 0.2.0 complains about setting some setting some status fields of the CR to invalid values on namespace creation, but keeps working. It logs the below error (human readable form here, raw details are below):
error:
stacktrace:
More details to replicate:
Operator is deployed with helm on a fresh minikube instance:
The namespaceconfig's status field is getting the updates:
I can see an error line from the operator when creating new namespace with a matching selector: