When applying the etc-pki-entitlement secret in an OpenShift build, an error is encountered due to the metadata.annotations field exceeding the size limit of 262144 bytes.

Our documentation should instruct admins to use server-side apply so that the metadata.annotations field does not explode.

    4.16 on top of OSP17.1

    Always

    1.
    2.
    3.
    

   Test case fails 

Impacted docs: https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html/builds_using_buildconfig/running-entitled-builds#builds-source-secrets-entitlements_running-entitled-builds

fail [github.com/openshift/origin/test/extended/builds/subscription_content.go:55]: creating secret etc-pki-entitlement
Unexpected error:
    <*fmt.wrapError | 0xc001897d40>:
    Error running /usr/local/bin/oc --namespace=e2e-test-build-subscription-content-7kbtn --kubeconfig=/tmp/configfile603472159 apply -f -:
    StdOut>
    The Secret "etc-pki-entitlement" is invalid: metadata.annotations: Too long: must have at most 262144 bytes
    StdErr>
    The Secret "etc-pki-entitlement" is invalid: metadata.annotations: Too long: must have at most 262144 bytes
    exit status 1
{
    msg: "Error running /usr/local/bin/oc --namespace=e2e-test-build-subscription-content-7kbtn --kubeconfig=/tmp/configfile603472159 apply -f -:\nStdOut>\nThe Secret \"etc-pki-entitlement\" is invalid: metadata.annotations: Too long: must have at most 262144 bytes\nStdErr>\nThe Secret \"etc-pki-entitlement\" is invalid: metadata.annotations: Too long: must have at most 262144 bytes\nexit status 1\n",
    err: <*exec.ExitError | 0xc001897d20>{
        ProcessState: {
            pid: 537188,
            status: 256,
            rusage: {
                Utime: {Sec: 0, Usec: 224613},
                Stime: {Sec: 0, Usec: 39183},
                Maxrss: 212436,
                Ixrss: 0,
                Idrss: 0,
                Isrss: 0,
                Minflt: 3671,
                Majflt: 0,
                Nswap: 0,
                Inblock: 0,
                Oublock: 0,
                Msgsnd: 0,
                Msgrcv: 0,
                Nsignals: 0,
                Nvcsw: 686,
                Nivcsw: 143,
            },
        },
        Stderr: nil,
    },
}occurred
Ginkgo exit error 1: exit with code 1