fix: Use rbac api group for bindings to sync nicely in ArgoCD #109
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Should resolved ArgoCD out of sync on these resources.
The nature of this problem is rooted in how Openshift handles
authorization.openshift.io
API. This API is being deprecated/replaced, since it was donated to upstream kubernetes. Hence when a manifest is submitted toauthorization.openshift.io
it gets accepted, but it is internally converted torbac.authorization.k8s.io
. That means the sync of the resource into the cluster is successful, but when ArgoCD tries to query for the resource, it no longer exists in this API group, hence it's reported missing by ArgoCD.