🐛 rbac: fix adding nonResourceURLs including normalisation

[chrischdi]

Fixes the rbac generator for nonResourceURLs / when using kubebuilder:rbac:urls marker.

Kudos to @rakesh-garimella for reporting it at #937

This propably broke when implementing #937

@sbueringer : I think this is ok to cherry-pick?

[sbueringer]

Thx!

/lgtm
/approve

/test pull-controller-tools-test-master

[k8s-ci-robot]

@sbueringer: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test pull-controller-tools-test-main

Use /test all to run all jobs.

In response to this:

Thx!

/lgtm
/approve

/test pull-controller-tools-test-master

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: ef6decf5935fc4c5b0a8fd97bf141fd7825615df

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrischdi, sbueringer

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sbueringer]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sbueringer]

/cherry-pick release-0.16

[sbueringer]

@rakesh-garimella Do you have some time to verify the fix on your side as well? I would then cut a new patch release

[k8s-infra-cherrypick-robot]

@sbueringer: cannot checkout release-0.16: error checking out "release-0.16": exit status 1 error: pathspec 'release-0.16' did not match any file(s) known to git

In response to this:

/cherry-pick release-0.16

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[sbueringer]

Just remembered that we don't always use release branches in CT, which is also the reason why we don't have one yet.

I would also cut this patch release directly from main, because apart from a few bug fixes nothing was changed on CT main since v0.16 & v0.16.1.

(we only have pre-submit jobs set up for the main branch in CT)

[rakesh-garimella]

thanks @sbueringer I will give it a try

[rakesh-garimella]

The fix works for me, thanks again @chrischdi @sbueringer

[sbueringer]

Thx again for reporting!