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
while testing binding to an APIExport in a different workspace, @fabriziopandini and I noticed that binding to an export with a . in the name is not working when using kubectl kcp bind apiexport. when applying the APIBinding resource everything works as expected
Steps To Reproduce
create an APIExport with a . (e.g. bar.dev) in the name in workspace foo
from another workspace run kubectl kcp bind apiexport root:foo:bar.dev --name bar-binding
you will get the following:
error: fully qualified reference to workspace where APIExport exists is required. The format is `<logical-cluster-name>:<apiexport>` or `<full>:<path>:<to>:<apiexport>`
Expected Behaviour
I would expect the bind to succeed
Additional Context
tested from the main branch
The text was updated successfully, but these errors were encountered:
yastij
changed the title
bug: kubectl kcp bind apiexport does not support . in name
bug: kubectl kcp bind apiexport does not support . in APIExport name
Feb 8, 2023
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
kcp-ci-bot
added
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
May 15, 2024
Describe the bug
while testing binding to an APIExport in a different workspace, @fabriziopandini and I noticed that binding to an export with a
.
in the name is not working when usingkubectl kcp bind apiexport
. when applying theAPIBinding
resource everything works as expectedSteps To Reproduce
.
(e.g.bar.dev
) in the name in workspacefoo
kubectl kcp bind apiexport root:foo:bar.dev --name bar-binding
Expected Behaviour
I would expect the bind to succeed
Additional Context
tested from the
main
branchThe text was updated successfully, but these errors were encountered: