Skip to content

Verrazzano release v1.6.0
Compare
Choose a tag to compare
@verrazzanobot verrazzanobot released this 28 Jun 17:20
v1.6.0
c04ecd4
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Features:

  • Added support for creating OCNE clusters from the console.
  • Added Thanos, which supports high availability and long-term metrics storage on top of Prometheus.
  • Added Fluent Operator, which, if you enable it, allows the use of Fluent Bit for log processing.

Enhancements:

  • Enhanced the Verrazzano CLI to support installing and upgrading from a private registry and in disconnected environments.
  • Now, you can use customer-managed cert-manager instances with Verrazzano.
  • Added support for Kubernetes v1.25 and v1.26.

Component version updates:

  • Argo CD v2.7.2
  • Coherence Operator v3.2.10
  • Jaeger v1.42.0
  • kube-state-metrics v2.8.2
  • NGINX Ingress Controller v1.7.1
  • Prometheus Operator v0.64.1
  • Prometheus v2.44.0
  • Rancher v2.7.3
    • Rancher Partner charts and RKE2 charts are no longer bundled.
  • Rancher Backup Operator v3.1.0
  • WebLogic Kubernetes Operator v4.0.6
  • WebLogic Monitoring Exporter v2.1.3

Components added:

  • cert-manager webhook for Oracle Cloud Infrastructure DNS v0.1.0
  • Cluster API v1.4.2
  • Fluent Operator v2.2.0
  • Thanos v0.30.2

Fixes:

  • Disabled the startupapicheck job in cert-manager startup.
  • Fixed an issue with Rancher SSO via Keycloak when using a custom CA for Verrazzano certificates.
  • Fixed an issue where not defining the replicas for default OpenSearch node pools in the Verrazzano CR caused the pods to terminate.
  • Updated the base image and other component images to resolve CVEs.

Known issues and workarounds:

  • Systemd journal logs are not collected on some platforms. The systemd plugin for Fluentd cannot read systemd journal files on Kubernetes nodes that use newer versions of systemd. This is known to impact the default node images of kind for Kubernetes 1.24 and later, Oracle Linux 9, and any other Kubernetes cluster nodes running on an operating system that has systemd version 246 or later.
  • Registration of managed clusters using the Verrazzano console is not working in disconnected environments. Use the Kubernetes Custom Resources method instead.
Assets 12