There is an issue in OpenShift resources when resourceVersion is included in the kubectl.kubernetes.io/last-applied-configuration annotation. This behavior does not occur in native Kubernetes resources.

oc version
Client Version: 4.18.1
Kustomize Version: v5.4.2
Server Version: 4.18.2
Kubernetes Version: v1.31.6    

 Steps to Reproduce:   

Create a new namespace:

oc create ns test-3

Apply the initial BuildConfig:

apply -f https://raw.githubusercontent.com/Mangaal/argocd-resource-version-issue/refs/heads/main/manifest/bc.yaml

Retrieve and inspect the BuildConfig 

oc get buildconfig -n test-3 core -o yaml
oc get buildconfig -n test-3 core -o yaml > core.yaml

Reapply the saved YAML file, which now includes the latest metadata.resourceVersion:
oc apply -f core.yaml

Verify that resourceVersion is included in the annotation:

oc get buildconfig core -n test-3 -o jsonpath="{.metadata.annotations.kubectl\.kubernetes\.io/last-applied-configuration}" | jq

The resourceVersion is present in last-applied-configuration because the previously applied YAML contained it. Attempt to reapply the original YAML file:
oc apply -f https://raw.githubusercontent.com/Mangaal/argocd-resource-version-issue/refs/heads/main/manifest/bc.yaml

Observed Error:

The buildconfigs "core" is invalid: metadata.resourceVersion: Invalid value: 0x0: must be specified for an update

OpenShift resources like BuildConfig and Route encounter errors when reapplying YAML due to resourceVersionbeing included in the last-applied-configuration annotation.

The behavior should be consistent with Kubernetes native k8s resource (e.g., Deployment), where similar OpenShift resources (e.g., Route) do not have this issue.

  https://issues.redhat.com/browse/GITOPS-6009