knative-extensions / knative-extensions/kn-plugin-source-kamelet
For "binding create" multiple namespace options are required
- Dominant language
- Go
- Stars
- 2
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Currently, there is only a single `--namespace` option when creating a KameletBinding. However, there are multiple namespace fields that can be set:
* THe namespace of the binding itself
* The namespace of the `source:` ref
* The namespace of the `sink:` ref
Currently, the specified namespace is used for all three fields. Since cross-namespace references are not allowed, this often is not a problem. However, when referring to default Kamelets from the system namespace, there must a namespace set on the reference (as it would violate the "cross-namespace" constraint).
Maybe add something like `--namespace-source` and `--namespace-sink` ?
Contributor guide
Research direction
Start at the `binding create` command and trace how the current `--namespace` option is applied to the binding, source reference, and sink reference. Define separate source and sink namespace options, then verify that each namespace is assigned to the intended reference, including references to default Kamelets in the system namespace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100