Uploaded image for project: 'OpenShift Over the Air'
  1. OpenShift Over the Air
  2. OTA-209

Allow changing the log level of cluster-version-operator using API configuration

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • OTA 233, OTA 263

      The current way is

      ## Set the override for clusterversion to empty.```
      cat <<EOF >version-patch-empty-override.yaml
      - op: replace
        path: /spec/overrides
        value: []
      EOF
      ``````
      oc patch clusterversion version --type json --patch "$(cat version-patch-empty-override.yaml)"
      ```## Set the override to allow modifying the clusterversion operator log levels.```
      cat <<EOF >version-patch-add-override.yaml
      - op: add
        path: /spec/overrides/-
        value:
          group: apps/v1
          kind: Deployment
          name: cluster-version-operator
          namespace: openshift-cluster-version
          unmanaged: true
      EOF
      ``````
      oc patch clusterversion version --type json --patch "$(cat version-patch-add-override.yaml)"
      ```## Increase the log level for cluster-version-operator to 10```
      cat <<EOF >version-patch-log-override.yaml
      - op: replace
        path: /spec/template/spec/containers/0/args/3
        value: '--v=10'
      EOF
      ``````
      oc patch deployment cluster-version-operator --type json --patch "$(cat version-patch-log-override.yaml)" -n openshift-cluster-version
      ```

      We should improve this.

       

      Definition of Done:

      • The verbosity of the CVO's logs can be configured even when the CVO is running by modifying the ClusterVersion resource.

              dhurta@redhat.com David Hurta
              adahiyaredhat Abhinav Dahiya (Inactive)
              Jian Li Jian Li
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: