Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Module Upgrade: v1.8.0 #32

Merged
merged 12 commits into from
Jun 2, 2021
Merged

Module Upgrade: v1.8.0 #32

merged 12 commits into from
Jun 2, 2021

Conversation

angelbarrera92
Copy link
Contributor

Logging Core Module version 1.8.0

SIGHUP team maintains this module updated and tested. That is the main reason why we worked on this new release.
With the Kubernetes 1.21 release, it became the perfect time to start testing this module against this Kubernetes
release.

Continue reading the Changelog to discover them:

Changelog

Upgrade path

To upgrade this core module from v1.7.0 to v1.8.0, you need to download this new version, then apply the
kustomize project. No further action is required.

$ kustomize build katalog/cerebro | kubectl apply -f -
$ kustomize build katalog/curator | kubectl apply -f -
# or
$ kustomize build katalog/curator-s3 | kubectl apply -f -
$ kustomize build katalog/elasticsearch-single | kubectl apply -f -
# or
$ kustomize build katalog/elasticsearch-triple | kubectl apply -f -
$ kustomize build katalog/fluentd | kubectl apply -f -
$ kustomize build katalog/kibana | kubectl apply -f -

Important notes

Before upgrading the elasticsearch-{single,triple} and the kibana package we recommend ensuring you read and
understand the
elastic rolling-upgrade official documentation.

@angelbarrera92 angelbarrera92 self-assigned this Jun 1, 2021
@angelbarrera92 angelbarrera92 merged commit 51488b1 into master Jun 2, 2021
@angelbarrera92 angelbarrera92 deleted the upgrade-1.8 branch June 2, 2021 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant