No access to update ingresses/status subresource - OCP Dedicated

Solution In Progress - Updated -

Issue

  • I'm an administrator on our OpenShift Dedicated cluster, but the current RBAC rules don't appear to give me access to update the "status" subresource of "ingress" objects.
$ oc project
Using project "example" on server "https://example.dedicated-example.openshift.com:443"

$ oc policy can-i update 'ingresses'
yes

$ oc policy can-i update 'ingresses/status'
no
  • I'd like to have the same access to "ingresses/status" that I have on "routes/status"

Environment

OpenShift Dedicated

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content