...
When publishing a service definition, the operator definition is introspected for namespace definitions. If one is found, the CLI user will receive a warning.
...Talk about the openhorizon.service.kubernetesNamespace built-in property.....
Deployment:
A new field is added to the service section of a deployment policy, indicating the target namespace for the service's deployment.
...
- Uses this namespace as a built-in constraint when searching for deployment targets (nodes) that are not in the openhorizon-agent namespace.
- Ignores this namespace for nodes in the openhorizon-agent namespace (these nodes are assumed to have cluster scope permissions and are therefore valid targets for services in any namespace. That is, there is no built-in constraint on deployments for nodes in the openhorizon-agent namespace.
- Includes this namespace as built-in service property (openhorizon.service.kubernetesNamespace), so that the node owner can create constraint expressions referring to the target namespace of a service.
Note: The node owner is always free to configure a deployment constraint expression that limits the namespace
Patterns:
A new field is added to the schema of a pattern (as a top level field in the schema), indicating the target namespace for the pattern's deployment.
...