Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenShift support: add permission on ingress finalizer in k8gb rbac #816

Merged
merged 1 commit into from
Dec 23, 2021

Conversation

nicsmith
Copy link
Contributor

When creating an ingress resource (networking.k8s.io/v1) with annotations in OpenShift, k8gb does not create the corresponding gslb and logs the following error message:

ERR github.com/AbsaOSS/k8gb/controllers/gslb_controller.go:311 > Glsb creation failed error="gslbs.k8gb.absa.oss \"frontend-podinfo\" is forbidden: cannot set blockOwnerDeletion if an ownerReference refers to a resource you can't set finalizers on: , <nil>"

This fix grants the update permission on ingresses/finalizers in the k8gb ClusterRole so that Ingress resources can be used in OpenShift.

Tested on: OpenShift 4.8.25

Signed-off-by: Nicolas Smith nicolasasmith@gmail.com

When using ingress resources instead of routes in OpenShift, the update
permission is needed on ingresses/finalizers

Signed-off-by: Nicolas Smith <nicolasasmith@gmail.com>
Copy link
Collaborator

@k0da k0da left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@ytsarev ytsarev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, thank you for the contribution!

@ytsarev ytsarev merged commit 67c0a3d into k8gb-io:master Dec 23, 2021
@nicsmith nicsmith deleted the openshift-ingress-rbac branch December 23, 2021 12:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants