Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-5566

Add Annotations to the route created by LokiStack

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • VERIFIED
    • Before this update, the Loki Operator overwrite any user annotation on the LokiStack Route resource caused user customization to be dropped. With this update, the Loki Operator does not overwrite Route annotation anymore resolves the issue.
    • Bug Fix
    • Log Storage - Sprint 257, Log Storage - Sprint 258

      Goals : Add Annotation to LockiStack ressources

      I have noted that, when you add the annotations after the route ressource created, it is only removed during the upgrade of the operator.

      Non-Goals

      Motivation: After creating the LockiStack, i wanted to add annotations on route ressource created, and i want to keep those customs annotations even after the upgrade of the operator

      Alternatives

      Acceptance Criteria: Add annotations at the creation of the LockiStach

      Risk and Assumptions

      Documentation Considerations

      Open Questions

      Additional Notes

            [LOG-5566] Add Annotations to the route created by LokiStack

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Logging for Red Hat OpenShift - 6.0.0), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHBA-2024:6693

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Logging for Red Hat OpenShift - 6.0.0), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2024:6693

            Kabir Bharti added a comment - - edited

            Verified on loki-operator.v6.0.0.

            my-loki-instance-annotated": "true" is annotation applied.

            $ oc get route lokistack-dev -o json | jq -r .metadata.annotations
{
  "haproxy.router.openshift.io/timeout": "375s",
  "my-loki-instance-annotated": "true",
  "openshift.io/host.generated": "true"
}

            Kabir Bharti added a comment - - edited Verified on loki-operator.v6.0.0. my-loki-instance-annotated": "true" is annotation applied. $ oc get route lokistack-dev -o json | jq -r .metadata.annotations {   "haproxy.router.openshift.io/timeout" : "375s" ,   "my-loki-instance-annotated" : " true " ,   "openshift.io/host.generated" : " true " }

            GitLab CEE Bot added a comment -

            CPaaS Service Account mentioned this issue in merge request !4369 of openshift-logging / Log Storage Midstream on branch openshift-logging-6.0-rhel-9_upstream_9099f3fea92aca48ebec1d648a9f9285:

            Updated 2 upstream sources

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !4369 of openshift-logging / Log Storage Midstream on branch openshift-logging-6.0-rhel-9_ upstream _9099f3fea92aca48ebec1d648a9f9285 : Updated 2 upstream sources

            Joseph Severin Assiga Abouma added a comment -

            I have a customer engaged, he created a ticket here : https://github.com/openshift/loki/issues/303

            Joseph Severin Assiga Abouma added a comment - I have a customer engaged, he created a ticket here : https://github.com/openshift/loki/issues/303

              ptsiraki@redhat.com Periklis Tsirakidis
              jassigaa Joseph Severin Assiga Abouma
              Kabir Bharti Kabir Bharti
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: