RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
kube-addons.sh is trying to create the skydns-rc, but failed because of below:

# kubectl create -f skydns-rc.yaml 
error validating "skydns-rc.yaml": error validating data: [found invalid field successThreshold for v1.Probe, found invalid field failureThreshold for v1.Probe]; if you choose to ignore these errors, turn validation off with --validate=false

Could see "Liveness and readiness probes now support more configuration parameters: periodSeconds, successThreshold, failureThreshold"
under https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG.md/#other-notable-improvements.

Not sure if it apply to kubectl as well.

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


How reproducible:


Steps to Reproduce:
1. # kubectl create -f skydns-rc.yaml 
2.
3.

Actual results:
# kubectl create -f skydns-rc.yaml 
error validating "skydns-rc.yaml": error validating data: [found invalid field successThreshold for v1.Probe, found invalid field failureThreshold for v1.Probe]; if you choose to ignore these errors, turn validation off with --validate=false

Expected results:


Additional info:

Neither successThreshold nor failureThreshold are present in ~/.kube/schema/v1.2.0/api/v1/schema.json.

Guohua, can you remove ~/.kube/schema and re-run the ``kubectl create -f skydns-rc.yaml`` again"?

after remove ~/.kube/schema, the problem does not exist.

Anytime the apiserver is updated, ~/.kube/schema needs to be removed as the kubectl downloads the schema from apiserver. Once the schema is downloaded(=cached) it is never re-downloaded.