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
Prior to #2421, which substituted Namespaces []string for DefaultNamespaces map[string]Config, it used to be possible to combine DefaultLabelSelector, ByObject, and Namespaces like so:
This resulted in the controller's cache only including objects in the <OPERATOR_NAMESPACE> namespace with all Appian custom resources being included and only other resources matching app.kubernetes.io/name=appian being included
The config above is no longer possible. Now, one must do something like so:
This however, doesn't result in the same behavior. It still results in the controller's cache only including objects in the <OPERATOR_NAMESPACE> namespace, but the ByObject.Label configuration is ignored, meaning only Appian custom resources matching app.kubernetes.io/name=appian are included
The text was updated successfully, but these errors were encountered:
Prior to #2421, which substituted
Namespaces []string
forDefaultNamespaces map[string]Config
, it used to be possible to combineDefaultLabelSelector
,ByObject
, andNamespaces
like so:This resulted in the controller's cache only including objects in the
<OPERATOR_NAMESPACE>
namespace with all Appian custom resources being included and only other resources matchingapp.kubernetes.io/name=appian
being includedThe config above is no longer possible. Now, one must do something like so:
This however, doesn't result in the same behavior. It still results in the controller's cache only including objects in the
<OPERATOR_NAMESPACE>
namespace, but theByObject.Label
configuration is ignored, meaning only Appian custom resources matchingapp.kubernetes.io/name=appian
are includedThe text was updated successfully, but these errors were encountered: