Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-48077

Ratcheting validation does not work for status subresource

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • 4.18, 4.19
    • kube-apiserver
    • None
    • None
    • Approved
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      Description of problem:

      Ratcheting validation was implemented and made beta in 1.30.

Validation ratcheting works for changes to the main resource, but does not work when applying updates to a status subresource.

Details in https://github.com/kubernetes/kubernetes/issues/129503  

      Version-Release number of selected component (if applicable):

      How reproducible:

          Always

      Steps to Reproduce:

          1. Install 4.17
    2. Set powervs serviceEndpoints in the platformStatus to a valid lowercase string
    3. Upgrade to 4.18 - validation has changed
    4. Attempt to update an adjacent status field  

      Actual results:

          Validation fails and rejects the update

      Expected results:

          Ratcheting should kick in and accept the object

      Additional info:

              joelspeed Joel Speed
              joelspeed Joel Speed
              Ke Wang Ke Wang
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: