-
Notifications
You must be signed in to change notification settings - Fork 276
Description
What would you like to be added:
By default, NFD automatically adds its namespace (i.e., the prefix) to all extended resources and annotations it creates. However, in some cases, it may be desirable to suppress this behavior and omit the nfd prefix - similar to how labels can be configured without it. This provides more flexibility for users who wish to align with custom naming conventions or integrate with other systems that depends on certain pattern.
Why is this needed:
There may be external systems that rely on specific annotations or extended resources. In such cases, the presence of the NFD prefix could prevent those components from recognizing or properly handling the nodes, as the prefixed resources may not match their expected formats or naming conventions. Allowing the option to skip the NFD prefix ensures better compatibility with third-party tools and custom integrations.