Releases: vertica/vertica-kubernetes
Releases · vertica/vertica-kubernetes
Vertica Kubernetes 2.2.0
Added
- #743 Added a new upgrade policy - replicated upgrade. This upgrade policy allows the user to write during the upgrade. It's an advanced version of online upgrade
- #819 Added SourceVerticaDB, TargetVerticaDB, State, Age print columns to vrep for a better status check.
- #785 Allow the user to upgrade the subclusters in a sandbox through offline upgrade.
- #775 Allows the users to convert secondary subclusters to sandboxes.
- #740 Added a new CRD - VerticaReplicator. This CRD can be used to replicate data from a database/sandbox to another database/sandbox.
Changed
- #841 Renamed upgrade policy Online to ReadOnlyOnline, and renamed upgrade policy Replicated to Online.
Removed
- #827 Remove memory profiler from the operator.
Fixed
- #835 Ignore includeUIDInPath annotation when reviving db for locating the communal storage correctly.
Security
- #858 Fix for CVE-2024-24790
Vertica Kubernetes 2.0.3
Security
- #858 Fix for CVE-2024-24790
- #774 Fix for CVE-2023-45288
Vertica Kubernetes 1.11.3
Security
- #858 Fix for CVE-2024-24790
- #646 Fix for CVE-2023-48795
Vertica Kubernetes 2.1.3
Changed
- #781 VerticaRestorePointsQuery will minimize the number of retry attempts
Security
- #774 Fix for CVE-2023-45288
Vertica Kubernetes 2.1.2
Changed
- #746 Operator now defaults endpoints for S3/GCS paths
- #742 Change VerticaScrutinize to read password from file
Fixed
- #756 Fix restart logic for ScheduleOnly init policy
- #744 Update role to grant write permissions for new CRDs
- #739 Resolved Service Annotation Loop Issue in ROSA Environment
Security
- #758 Resolved security vulnerabilities in vertica-logger image
- #757 Fix for CVE-2024-24786
Vertica Kubernetes 2.1.1
Vertica Kubernetes 2.1.0
Added
- #728 New CRD, VerticaScrutinize, to run and collect scrutinize data for a VerticaDB
- #728 New CRD, VerticaRestorePointsQuery, that will show the restore points that exist for the database
- #728 Ability to specify a restore point in the VerticaDB to revive from
- #722 Experimental support to run the operator on arm64
- #719 Allow namespace scoped operator deployment
- #717 Reinstall packages during upgrade
Changed
- #725 Default value for prometheus.expose helm chart is now Disable
Deprecated
- #719 The logging helm chart parameters, except logging.level, are deprecated and will be removed in a future release.
Fixed
- #714 Surface event message when admintools deployment is selected with a v24.2.0 server
Vertica Kubernetes 2.0.2
Added
- #691 Configure createdb timeout by annotation vertica.com/createdb-timeout
- #683 Allow NMA health probes to be overridden with annotations
- #674 Set resources for NMA sidecar container
- #667 Add health probes to the NMA sidecar container
Changed
- #689 Support restricted SCC in OpenShift (depends on v24.2.0 server)
- #689 Auto detect NMA sidecar deployment and remove vertica.com/run-nma-in-sidecar annotation
- #667 Don't run vertica as a deamon process when deployed with the NMA sidecar container
Removed
- #689 s6-overlay init process in v2 server container to be released in v24.2.0.
Fixed
Vertica Kubernetes 2.0.1
Added
- #654 Support for running the NMA as a sidecar in 24.2.0 or newer.
- #636 Allow use of Amazon Secrets Manager for secret store
Changed
- #662 Drop CRD write permissions for OLM style deployments
- #653 Upgrade path detection now only blocks downgrades.
Fixed
- #655 Better handling when remove node is interrupted
- #652 Improve resilency of create db in low resource environments.
- #650 Requeue reconcile iteration if dependent object is removed in the middle of a reconcile
- #644 Allow upgrades across deployments when ignoring upgrade paths
Security
- #646 Fix for CVE-2023-48795
Vertica Kubernetes 2.0.0
Added
- #519 Add new v1 API for VerticaDB
- #563 Make the default deployment type for VertiacDB v1 API is vclusterops
- #618 Allow annotations to be added to the serviceAccount created through the helm chart.
- #611 Deploy the operator with kubectl command
- #597 Added a feature to allow the source of secrets to be specified with a secret path reference
- #577 Redirect startup.log to stdout
- #578 Ability to control the name of the superuser
- #521 Ability to specify pre-existing serviceAccount in the VerticaDB CR
Changed
- #624 Switched server container from ubuntu to rockylinux 9
- #590 Made 'spread channel encryption' a default behavior for database creation
- #556 Allow any uid/gid to be set for vertica pods
- #536 Enabling spread encryption no longer requires a cluster restart on server versions 23.3.0+.
- #524 Removed linux capabilities for vclusterOps deployments to make it easier to deploy in OpenShift
- #514 Change scope of operator from namespace to cluster
Deprecated
- #519 v1beta1 version of VerticaDB. Use v1 version now.
- #515 Deprecate the httpServerMode parameter in the VerticaDB CR
Removed
- #597 Removed the annotation "vertica.com/use-gcp-secret-manager"
- #519 webhook.caBundle helm chart parameter
- #508 Removed backdoor support for the Vertica agent
Fixed
- #633 Online upgrade to account for terminating pods
- #620 Add webhook validation to prevent subcluster service names that violate rfc 1035
- #619 Speed up revive when local paths in VerticaDB differ with communal storage
- #594 Webhook to calculate k-safety using primary nodes only
- #552 Timing hole that can skip the drain for scale down.
Security
- #574 Fix go project security vulnerabilities(GHSA-m425-mq94-257g, CVE-2023-39325, CVE-2023-3978)