oc export does not collect all of the information from daemonsets

Solution Verified - Updated -

Issue

  • Since deploying OCP 3.7 I have not been able to create / delete daemon sets via oc export.
oc export ds logging-fluentd -o yaml >> export-fluentd-ds.yaml

$ oc delete -f export-fluentd-ds.yaml 
error: unable to decode "export-fluentd-ds.yaml": Object 'Kind' is missing in '{"Spec":{"MinReadySeconds":0,"RevisionHistoryLimit":10,"Selector":{"matchLabels":{"component":"fluentd","provider":"openshift"}},"Template":{"Spec":{"ActiveDeadlineSeconds":null,"Affinity":null,"AutomountServiceAccountToken":null,"Containers":
  • oc export daemonset <DS_NAME> and oc get daemonset <DS_NAME> -o yaml collects different data in ocp 3.7 compared to ocp 3.6
  • In 3.6, the only difference in the output from get and export is that get includes some additional metadata that export excludes. In 3.7, there is a good bit of differences, most importantly the field "kind: DaemonSet" is missing in export.

Environment

  • Red Hat OpenShift Container Platform
    • 3.7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.