Armel Soro 7bd4d25de6 Allow binding to services from other namespaces (#5936) ...

* Allow Dynamic Client to list dynamic resources from a specified namespace

If the namespace specified is empty, it works as before
by returning resources from the current namespace.

Listing dynamic resources is used
when listing service binding instances.

* Allow users to select a namespace from which Service Binding Instances are retrieved

For consistency, this supports both interactive and non-interactive modes.
Non-interactive mode is supported via a '--service-namespace' flag.
As before, if this namespace is not specified, we default
to using the current namespace.

This also handles permission errors that might occur while listing namespaces/projects.
On Openshift, listing projects returns all the projects a user
effectively has access to, but this does not behave the same way
in vanilla K8s clusters. If user is allowed to list namespaces/projects,
the list returned is not filtered by any ACL filter [1].

In the case a user is not allowed to list namespaces/projects,
rather than returning an error, we are prompting them to manually
enter a different namespace (or nothing to use the current one).

[1] https://github.com/kubernetes/kubernetes/issues/48537

* Make the "No bindable service instances found" error message more explicit by mentioning the namespace

* Add namespace information to service (with or without Devfile)

* Add namespace information to 'list binding' and 'describe binding' output

* Check SBO availability before user is asked questions

2022-07-21 18:44:05 +02:00

..

interface.go

Allow binding to services from other namespaces (#5936)

2022-07-21 18:44:05 +02:00

survey_asker.go

Allow binding to services from other namespaces (#5936)

2022-07-21 18:44:05 +02:00