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
Ah apologies, that was an experiment to auto generate the rbac as part of the CLI tooling. The client-go handling of rbac generation is quite difficult so I never completed it. 😐
If that is not going to be completed, maybe, include the rbac.yml as a static file, and return that from that go codepath?
My hope is to have a straightforward way to match the rbac.yml version with the kube-vip version. Preferably, it should came from the same binary or artifact, so we just need to download one thing. That way, we have no doubts whether the rbac manifest is compatible with the specific kub-vip version.
Describe the bug
With the v0.7.0 release, the rbac manifest ceased being available inside the git repository as it was in the previous versions (e.g. at https://github.com/kube-vip/kube-vip/blob/v0.6.4/docs/manifests/rbac.yaml) and started to be available at https://kube-vip.io/manifests/rbac.yaml.
Looking for a versioned alternative, I've found
kube-vip manifest rbac
, which seemed to return the expected rbac manifest, but instead, it returns:Which I think is a bug, and it should have returned the same document that is currently at https://kube-vip.io/manifests/rbac.yaml.
To Reproduce
Steps to reproduce the behavior:
kube-vip manifest rbac
Expected behavior
I expected it to return the same document as the one available at https://kube-vip.io/manifests/rbac.yaml.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: