Skip to content

fix: grant RBAC for events.k8s.io Events emitted by the events/v1 recorder - #391

Open
xrl wants to merge 1 commit into
etcd-io:mainfrom
xrl:pr/fix-events-rbac
Open

xrl wants to merge 1 commit into
etcd-io:mainfrom
xrl:pr/fix-events-rbac

Conversation

@xrl

@xrl xrl commented Jul 2, 2026 •

Copy link
Copy Markdown

SetupWithManager wires r.Recorder = mgr.GetEventRecorder(...), an events.k8s.io/v1 recorder, but role.yaml only grants events verbs in the core ("") group. The first Event the operator emits will be rejected by the API server (cannot create resource "events" in API group "events.k8s.io"), and kubectl describe etcdcluster shows Events: <none>. envtest doesn't enforce RBAC, so tests don't catch it.

On main the recorder isn't called yet, so this is latent; it bites as soon as the workflows start emitting Events (recreate/replace/NOSPACE are natural places). This adds an events.k8s.io create;patch RBAC marker (the verbs the tools/events broadcaster uses) and regenerates config/rbac/role.yaml.

Rebased onto main after the #362 rewrite. make test and make lint pass; make manifests shows no drift.

@kubernetes-prow

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: xrl
Once this PR has been reviewed and has the lgtm label, please assign jberkus for approval. For more information see the Code Review Process.

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

Details Needs approval from an approver in each of these files:

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

@kubernetes-prow

Copy link
Copy Markdown

Hi @xrl. Thanks for your PR.

I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

xrl added a commit to xrl/etcd-operator that referenced this pull request Jul 7, 2026
…d Role

The overlay role.yaml predates fix etcd-io#391 (events/v1 recorder writes to
events.k8s.io, not core/v1); without this rule every operator Event is
rejected in the namespace-scoped deployment.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Xavier Lange <xrlange@gmail.com>
xrl added a commit to xrl/etcd-operator that referenced this pull request Jul 11, 2026
The recorder returned by mgr.GetEventRecorder writes events.k8s.io/v1
Events, but role.yaml only granted events verbs in the core API group,
so every TLSReady event (including the new ClientCABroadTrust warning)
was silently dropped. Mirrors the standalone fix in etcd-io#391; whichever
lands first, the other rebases to a no-op.

Signed-off-by: Xavier Lange <xrlange@gmail.com>
…order

The recorder returned by mgr.GetEventRecorder writes events.k8s.io/v1
Events, but role.yaml only granted events verbs in the core ("") API
group, so the API server rejects every operator-emitted Event on real
clusters (envtest does not enforce RBAC):

  Server rejected event (will not retry!) ... cannot create resource
  "events" in API group "events.k8s.io"

Add an events.k8s.io events create;patch RBAC marker (the two verbs the
client-go tools/events broadcaster uses) and regenerate role.yaml.

Signed-off-by: Xavier Lange <xrlange@gmail.com>
@xrl
xrl force-pushed the pr/fix-events-rbac branch from aae6fe2 to 13249ca Compare October 8, 2026 16:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant