Release v4.0.0

Logging Core Module Release 4.0.0

Welcome to the latest release of the logging module of Kubernetes Fury Distribution maintained by team SIGHUP.

This update is a major version that adds support for the Kubernetes version 1.30 and 1.31. It also introduces a breaking change with the new time series database for Loki TSDB along with the new v13 schema.
These changes will improve efficiency, speed and scalability of Loki clusters.

Component Images 🚢

Component	Supported Version	Previous Version
opensearch	v2.17.1	2.12.0
opensearch-dashboards	v2.17.1	2.12.0
logging-operator	v4.10.0	4.5.6
loki-distributed	v2.9.10	2.9.2
minio-ha	RELEASE.2024-10-13T13-34-11Z	RELEASE.2023-01-12T02-06-16Z

Bug Fixes and Changes 🐛

• Added support for Kubernetes version 1.30 and 1.31

• New schema and store for Loki: The Loki configuration has been extended to add the new TSDB store and v13 schema. There are two new elements in the configuration (note: this is a breaking change):

  ...
  schema_config:
    ...
    - from: "2024-12-01"
      index:
        period: 24h
        prefix: index_
      object_store: s3
      schema: v13
      store: tsdb
  ...
  storage_config:
    ...
    tsdb_shipper:
      active_index_directory: /var/loki/index
      cache_location: /var/loki/cache
      cache_ttl: 24h
      resync_interval: 5s
      shared_store: s3

  The two pieces of new configuration introduced are:

  • The new schema config with TSDB and schema v13
  • The tsdb_shipper conf that configures the storage for TSDB

  The from in schema_config should be a string in ISO 8601 date format and it represents the day starting from which Loki will record logs with the new store and schema.

  ℹ️ Note: Loki will assume the start of the day on the UTC midnight of the specified day.

Breaking Changes 💔

• Loki store and schema change: A new store and schema has been introduced in order to improve efficiency, speed and scalability of Loki clusters.

Update Guide 🦮

⚠ Before upgrading read about the changes in Loki schema and store

Upgrade using the distribution

To upgrade the module using the distribution please refer to the official documentation

Manual Upgrade

ℹ️ Note: Manually upgrading the module is deprecated. It is reccommended to use fury distribution

To upgrade the module run:

kustomize build | kubectl apply -f -

Preview v4.0.0-rc.3

Logging Core Module Release 4.0.0

Welcome to the latest release of the logging module of Kubernetes Fury Distribution maintained by team SIGHUP.

This update is a major version that adds support for the Kubernetes version 1.30 and 1.31. It also introduces a breaking change with the new time series database for Loki TSDB along with the new v13 schema.
These changes will improve efficiency, speed and scalability of Loki clusters.

Component Images 🚢

Component	Supported Version	Previous Version
opensearch	v2.17.1	2.12.0
opensearch-dashboards	v2.17.1	2.12.0
logging-operator	v4.10.0	4.5.6
loki-distributed	v2.9.10	2.9.2
minio-ha	RELEASE.2024-10-13T13-34-11Z	RELEASE.2023-01-12T02-06-16Z

Bug Fixes and Changes 🐛

• Added support for Kubernetes version 1.30 and 1.31

• New schema and store for Loki: The Loki configuration has been extended to add the new TSDB store and v13 schema. There are two new elements in the configuration (note: this is a breaking change):

  ...
  schema_config:
    ...
    - from: "2024-12-01"
      index:
        period: 24h
        prefix: index_
      object_store: s3
      schema: v13
      store: tsdb
  ...
  storage_config:
    ...
    tsdb_shipper:
      active_index_directory: /var/loki/index
      cache_location: /var/loki/cache
      cache_ttl: 24h
      resync_interval: 5s
      shared_store: s3

  The two pieces of new configuration introduced are:

  • The new schema config with TSDB and schema v13
  • The tsdb_shipper conf that configures the storage for TSDB

  The from in schema_config should be a string in ISO 8601 date format and it represents the day starting from which Loki will record logs with the new store and schema.

  ℹ️ Note: Loki will assume the start of the day on the UTC midnight of the specified day.

Breaking Changes 💔

• Loki store and schema change: A new store and schema has been introduced in order to improve efficiency, speed and scalability of Loki clusters.

Update Guide 🦮

⚠ Before upgrading read about the changes in Loki schema and store

Upgrade using the distribution

To upgrade the module using the distribution please refer to the official documentation

Manual Upgrade

ℹ️ Note: Manually upgrading the module is deprecated. It is reccommended to use fury distribution

To upgrade the module run:

kustomize build | kubectl apply -f -

Preview v4.0.0-rc.1

Logging Core Module Release 4.0.0

Welcome to the latest release of the logging module of Kubernetes Fury Distribution maintained by team SIGHUP.

This update is a major version that adds support for the Kubernetes version 1.30 and 1.31. It also introduces a breaking change with the new time series database for Loki TSDB along with the new v13 schema.
These changes will improve efficiency, speed and scalability of Loki clusters.

Component Images 🚢

Component	Supported Version	Previous Version
opensearch	v2.17.1	2.12.0
opensearch-dashboards	v2.17.1	2.12.0
logging-operator	v4.10.0	4.5.6
loki-distributed	v2.9.10	2.9.2
minio-ha	RELEASE.2024-10-13T13-34-11Z	RELEASE.2023-01-12T02-06-16Z

Bug Fixes and Changes 🐛

• Added support for Kubernetes version 1.30 and 1.31

• New schema and store for Loki: The Loki configuration has been extended to add the new TSDB store and v13 schema. There are two new elements in the configuration (note: this is a breaking change):

  ...
  schema_config:
    ...
    - from: "2024-12-01"
      index:
        period: 24h
        prefix: index_
      object_store: s3
      schema: v13
      store: tsdb
  ...
  storage_config:
    ...
    tsdb_shipper:
      active_index_directory: /var/loki/index
      cache_location: /var/loki/cache
      cache_ttl: 24h
      resync_interval: 5s
      shared_store: s3

  The two pieces of new configuration introduced are:

  • The new schema config with TSDB and schema v13
  • The tsdb_shipper conf that configures the storage for TSDB

  The from in schema_config should be a string in ISO 8601 date format and it represents the day starting from which Loki will record logs with the new store and schema.

  ℹ️ Note: Loki will assume the start of the day on the UTC midnight of the specified day.

Breaking Changes 💔

• Loki store and schema change: A new store and schema has been introduced in order to improve efficiency, speed and scalability of Loki clusters.

Update Guide 🦮

⚠ Before upgrading read about the changes in Loki schema and store

Upgrade using the distribution

To upgrade the module using the distribution please refer to the official documentation

Manual Upgrade

ℹ️ Note: Manually upgrading the module is deprecated. It is reccommended to use fury distribution

To upgrade the module run:

kustomize build | kubectl apply -f -

Preview v4.0.0-rc.0

Logging Core Module Release 4.0.0

Welcome to the latest release of the logging module of Kubernetes Fury Distribution maintained by team SIGHUP.

This update is a major version that adds support for the Kubernetes version 1.30 and 1.31. It also introduces a breaking change with the new time series database for Loki TSDB along with the new v13 schema.
These changes will improve efficiency, speed and scalability of Loki clusters.

Component Images 🚢

Component	Supported Version	Previous Version
opensearch	v2.17.1	2.12.0
opensearch-dashboards	v2.17.1	2.12.0
logging-operator	v4.10.0	4.5.6
loki-distributed	v2.9.10	2.9.2
minio-ha	RELEASE.2024-10-13T13-34-11Z	RELEASE.2023-01-12T02-06-16Z

Bug Fixes and Changes 🐛

• Added support for Kubernetes version 1.30 and 1.31

• New schema and store for Loki: The Loki configuration has been extended to add the new TSDB store and v13 schema. There are two new elements in the configuration (note: this is a breaking change):

  ...
  schema_config:
    ...
    - from: "2024-12-01"
      index:
        period: 24h
        prefix: index_
      object_store: s3
      schema: v13
      store: tsdb
  ...
  storage_config:
    ...
    tsdb_shipper:
      active_index_directory: /var/loki/index
      cache_location: /var/loki/cache
      cache_ttl: 24h
      resync_interval: 5s
      shared_store: s3

  The two pieces of new configuration introduced are:

  • The new schema config with TSDB and schema v13
  • The tsdb_shipper conf that configures the storage for TSDB

  The from in schema_config should be a string in ISO 8601 date format and it represents the day starting from which Loki will record logs with the new store and schema.

  ℹ️ Note: Loki will assume the start of the day on the UTC midnight of the specified day.

Breaking Changes 💔

• Loki store and schema change: A new store and schema has been introduced in order to improve efficiency, speed and scalability of Loki clusters.

Update Guide 🦮

⚠ Before upgrading read about the changes in Loki schema and store

Upgrade using the distribution

To upgrade the module using the distribution please refer to the official documentation

Manual Upgrade

ℹ️ Note: Manually upgrading the module is deprecated. It is reccommended to use fury distribution

To upgrade the module run:

kustomize build | kubectl apply -f -

Preview v3.5.0-rc.1

Logging Core Module Release 3.5.0

Welcome to the latest release of the logging module of Kubernetes Fury Distribution maintained by team SIGHUP.

This update is a minor patch with a little fix on ingress fluentd outputs

Component Images 🚢

Component	Supported Version	Previous Version
opensearch	v2.17.1	2.12.0
opensearch-dashboards	v2.17.1	2.12.0
logging-operator	v4.10.0	4.5.6
loki-distributed	v2.9.10	2.9.2
minio-ha	RELEASE.2024-10-13T13-34-11Z	RELEASE.2023-01-12T02-06-16Z

Bug Fixes and Changes 🐛

• Added support for Kubernetes version 1.30 and 1.31

Update Guide 🦮

Process

To upgrade the module run:

kustomize build | kubectl apply -f -

Preview v3.5.0-rc.0

Logging Core Module Release 3.5.0

Welcome to the latest release of the logging module of Kubernetes Fury Distribution maintained by team SIGHUP.

This update is a minor patch with a little fix on ingress fluentd outputs

Component Images 🚢

Component	Supported Version	Previous Version
opensearch	v2.17.1	2.12.0
opensearch-dashboards	v2.17.1	2.12.0
logging-operator	v4.10.0	4.5.6
loki-distributed	v2.9.10	2.9.2
minio-ha	RELEASE.2024-10-13T13-34-11Z	RELEASE.2023-01-12T02-06-16Z

Bug Fixes and Changes 🐛

• Added support for Kubernetes version 1.30 and 1.31

Update Guide 🦮

Process

To upgrade the module run:

kustomize build | kubectl apply -f -

Release v3.4.1

Logging Core Module Release 3.4.1

Welcome to the latest release of the logging module of Kubernetes Fury Distribution maintained by team SIGHUP.

This update is a minor patch with a little fix on ingress fluentd outputs

Component Images 🚢

Component	Supported Version	Previous Version
opensearch	v2.12.0	No update
opensearch-dashboards	v2.12.0	No update
logging-operator	v4.5.6	No update
loki-distributed	v2.9.2	No update
minio-ha	vRELEASE.2023-01-12T02-06-16Z	No update

Bug Fixes and Changes 🐛

• fix: keep k8s labels for ingress-flow @ralgozino

Update Guide 🦮

Process

To upgrade the module run:

kustomize build | kubectl apply -f -

Release v3.4.0

Logging Core Module Release 3.4.0

Welcome to the latest release of the logging module of Kubernetes Fury Distribution maintained by team SIGHUP.

This update includes new versions of various components, removes Cerebro, and adds support for Kubernetes 1.28 and 1.29.

Component Images 🚢

Component	Supported Version	Previous Version
cerebro	removed	0.9.4
opensearch	v2.12.0	2.11.0
opensearch-dashboards	v2.12.0	2.11.0
logging-operator	v4.5.6	4.4.1
loki-distributed	v2.9.2	No update
minio-ha	vRELEASE.2023-01-12T02-06-16Z	No update

Bug Fixes and Changes 🐛

• Added support for Kubernetes versions 1.28 and 1.29.
• Removed Cerebro
• Add positiondb hostPath /var/log/infra-fluentbit-pos to persist fluentbit log forward history

Update Guide 🦮

Process

To upgrade the module, follow the next steps:

1. If you had Cerebro installed, you may want to remove it from the cluster using the copy in your vendor folder:

kustomize build vendor/katalog/logging/cerebro | kubectl delete -f -

2. Download the new version of the module
3. Update the rest of the packages:

kustomize build | kubectl apply -f -

Remove Cerebro after upgrading

If you don't have a local copy of Cerebro on your vendor folder, run the following commands to remove it:

kubectl delete deployment -n logging cerebro
kubectl delete service -n logging cerebro

Identify the name for Cerebro's configmap and delete it:

# get all the configmaps that the name starts with cerebro-config
kubectl get configmap -n logging -ojson | jq -r '.items[] | select(.metadata.name | startswith("cerebro-config")) | .metadata.name'
# validate that the output it valid, then remove all of them
kubectl get configmap -n logging -ojson | jq -r '.items[] | select(.metadata.name | startswith("cerebro-config")) | .metadata.name' | xargs kubectl delete configmap -n logging

Preview v3.4.0-rc.11

Logging Core Module Release 3.4.0

Welcome to the latest release of the logging module of Kubernetes Fury Distribution maintained by team SIGHUP.

This update includes new versions of various components, removes Cerebro, and adds support for Kubernetes 1.28 and 1.29.

Component Images 🚢

Component	Supported Version	Previous Version
cerebro	removed	0.9.4
opensearch	v2.12.0	2.11.0
opensearch-dashboards	v2.12.0	2.11.0
logging-operator	v4.5.6	4.4.1
loki-distributed	v2.9.2	No update
minio-ha	vRELEASE.2023-01-12T02-06-16Z	No update

Bug Fixes and Changes 🐛

• Added support for Kubernetes versions 1.28 and 1.29.
• Removed Cerebro

Update Guide 🦮

Process

To upgrade the module, follow the next steps:

1. If you had Cerebro installed, you may want to remove it from the cluster using the copy in your vendor folder:

kustomize build vendor/katalog/logging/cerebro | kubectl delete -f -

2. Download the new version of the module
3. Update the rest of the packages:

kustomize build | kubectl apply -f -

Remove Cerebro after upgrading

If you don't have a local copy of Cerebro on your vendor folder, run the following commands to remove it:

kubectl delete deployment -n logging cerebro
kubectl delete service -n logging cerebro

Identify the name for Cerebro's configmap and delete it:

# get all the configmaps that the name starts with cerebro-config
kubectl get configmap -n logging -ojson | jq -r '.items[] | select(.metadata.name | startswith("cerebro-config")) | .metadata.name'
# validate that the output it valid, then remove all of them
kubectl get configmap -n logging -ojson | jq -r '.items[] | select(.metadata.name | startswith("cerebro-config")) | .metadata.name' | xargs kubectl delete configmap -n logging

Preview v3.4.0-rc.10

Logging Core Module Release 3.4.0

Welcome to the latest release of the logging module of Kubernetes Fury Distribution maintained by team SIGHUP.

This update includes new versions of various components, removes Cerebro, and adds support for Kubernetes 1.28 and 1.29.

Component Images 🚢

Component	Supported Version	Previous Version
cerebro	removed	0.9.4
opensearch	v2.12.0	2.11.0
opensearch-dashboards	v2.12.0	2.11.0
logging-operator	v4.5.6	4.4.1
loki-distributed	v2.9.2	No update
minio-ha	vRELEASE.2023-01-12T02-06-16Z	No update

Bug Fixes and Changes 🐛

• Added support for Kubernetes versions 1.28 and 1.29.
• Removed Cerebro

Update Guide 🦮

Process

To upgrade the module, follow the next steps:

1. If you had Cerebro installed, you may want to remove it from the cluster using the copy in your vendor folder:

kustomize build vendor/katalog/logging/cerebro | kubectl delete -f -

2. Download the new version of the module
3. Update the rest of the packages:

kustomize build | kubectl apply -f -

Remove Cerebro after upgrading

If you don't have a local copy of Cerebro on your vendor folder, run the following commands to remove it:

kubectl delete deployment -n logging cerebro
kubectl delete service -n logging cerebro

Identify the name for Cerebro's configmap and delete it:

# get all the configmaps that the name starts with cerebro-config
kubectl get configmap -n logging -ojson | jq -r '.items[] | select(.metadata.name | startswith("cerebro-config")) | .metadata.name'
# validate that the output it valid, then remove all of them
kubectl get configmap -n logging -ojson | jq -r '.items[] | select(.metadata.name | startswith("cerebro-config")) | .metadata.name' | xargs kubectl delete configmap -n logging