Details
-
Task
-
Resolution: Done
-
Undefined
-
None
-
None
-
2
-
False
-
None
-
False
-
NEW
-
OBSDA-7 - Adopting Loki as an alternative to Elasticsearch to support more lightweight, easier to manage/operate storage scenarios
-
VERIFIED
-
Logging (LogExp) - Sprint 216
Description
Upstream Changes
The Loki-Operator ClusterServiceVersion in upstream should provide the following:
The annotation for a suggested namespace should be provided only by the overlay config/overlays/openshift as such:
annotations: operatorframework.io/suggested-namespace: openshift-operators-redhat
The range start for OLM Skip range annotation should be:
annotations:
olm.skipRange: '>=5.4.0-0 <5.5.0'
The labels for supported architectures for all users of config/manifests/bases/loki-operator.clusterserviceverion.yaml:
labels: operatorframework.io/arch.amd64: supported operatorframework.io/arch.arm64: supported operatorframework.io/arch.ppc64le: supported operatorframework.io/arch.s390x: supported
The default channel declared in the Makefile and generated in the bundle/metadata/annotations.yaml should be (See OLM Naming Conventions):
operators.operatorframework.io.bundle.channels.v1: candidate
Downstream Changes
The Loki-Operator ClusterServiceVersion in downstream should provide additionally the following:
A spec.relatedImages section (See similar to elasticsearch-operator-bundle).
The spec.provider.name should be Red Hat.
The spec.maintainers list should be replace by:
maintainers:
- email: aos-logging@redhat.com
name: Red Hat, AOS Logging
The metadata.annotations.olm.skipRange should be:
olm.skipRange: '>=5.4.0-0 <5.4.0-3'
Attachments
Issue Links
- incorporates
-
LOG-2218 support ARM64 for loki-operator images
-
- Closed
-
- links to
