Uploaded image for project: 'Maistra'
  1. Maistra
  2. MAISTRA-2677

SMCP does not support setting logging levels only for istiod

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • maistra-2.1.0
    • federation, operator
    • None
    • False
    • False

      The SMCP seems to provide two fields for configuring logging: .spec.general.logging and .spec.proxy.logging. Whatever you set in spec.general.logging.componentLevels gets applied to istiod, the default gateways and apparently the istio sidecar.

      When I tried to enable debug logging for federation by adding the following to the SMCP:

      spec:
  general:
    logging:
      componentLevels:
        federation: debug

      the SMCP failed to reconcile fully, because the gateway pods failed to start:

      $ kubectl get pods
NAME                                    READY   STATUS             RESTARTS   AGE
istio-egressgateway-84dcf8f848-x9tsn    0/1     CrashLoopBackOff   5          3m44s
istio-ingressgateway-5494c7cc6f-gcqzc   0/1     CrashLoopBackOff   5          3m44s
istiod-minimal-6cd6b844f6-s2jkt         1/1     Running            0          3m43s
wasm-cacher-minimal-7b8dff94cf-vw7lz    1/1     Running            0          3m43s

      They crash because the federation logging scope isn't registered:

      $ kubectl logs istio-egressgateway-84dcf8f848-x9tsn
Error: unknown scope 'federation' specified
2021-09-20T12:44:04.842449Z     error   unknown scope 'federation' specified

      We either need to make it possible to set a separate logging config for istiod or ensure that the gateways don't terminate when an unregistered log scope is configured.

              Unassigned Unassigned
              mluksa@redhat.com Marko Luksa
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: