Open
Conversation
Contributor
Author
|
renovate
bot
force-pushed
the
renovate/minor-dependencies
branch
5 times, most recently
from
8416af7 to
3580463
Compare
renovate
bot
force-pushed
the
renovate/minor-dependencies
branch
from
3580463 to
f7fe8d6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.23.2->v0.26.1v1.5.0->v1.6.0v0.2.0-rc2->v0.4.4v0.0.0-20190128024246-5eb7ae5bdb7a->v0.35.0v0.68.0->v0.85.0v0.0.0-20241202185148-04649f379358->v0.2.4v0.0.0-20240919204204-3da2ae0cabd1->v0.63.1v0.33.1->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v0.33.1->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v0.33.1->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v1.31.12->v1.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v0.31.5->v0.34.1v1.5.0->v1.6.0v1.5.0->v1.6.0v1.5.0->v1.6.0v1.6.8->v1.11.1v0.19.7->v0.22.1Release Notes
google/cel-go (github.com/google/cel-go)
v0.26.1Compare Source
What's Changed
proto.Messageby @srikrsna in #1207New Contributors
Full Changelog: google/cel-go@v0.25.1...v0.26.1
v0.26.0Compare Source
New Features ✨
Bug Fixes 🐛
Test Updates 🧪
Documentation 📚
Dependency Updates ⬆️
v0.25.1Compare Source
v0.25.0Compare Source
Features & Enhancements
This release introduces features for richer configuration-based CEL, AI prompt generation from config files, additional documentation, and 3x performance when evaluating traced / state-tracking expressions. This release also introduces a unit test runner framwork.
#1141: Expose extension option factory as a public method
#1143: Add a new compiler tool which can be used to compile CEL expressions and policies using serialized environment
#1151: Lightweight observable evaluation
#1155: Utilities for formatting and parsing documentation strings
#1156: Support for documentation and example strings in CEL environments
#1158: Re-export interpreter.AttributePattern in package cel.
#1159: Document the standard library macros and functions
#1160: Prompt generation for AI-assisted authoring based on a CEL environment
#1117: Add LateFunctionBinding declaration and fix constant folding
#1163: Initialize stateful observers prior to evaluation
#1164: Unparse Expr values to strings
#1149: Add test runner library
#1167: REPL: Add an extension option for two var comprehensions
Fixes
Several fixes were implemented, including updating strings.format to better adhere to the specification, correcting constant folding logic alongside the late binding feature, removing a non-functional check in test code, and adding argument count validation for optFieldSelect.
#1133: Update strings.format to adhere to the specification
#1117: Add LateFunctionBinding declaration and fix constant folding
#1161: Remove non-functional optional check in test-only selection
#1168: Check arg count when validating optFieldSelect
Refactoring & Internal Improvements
General refactoring was performed across the codebase. Coverage and comments for Activation methods were improved. The test runner library was refactored to create options from flags and improve code structure.
#1145: Refactoring changes
#1150: Additional comments and coverage for Activation methods
#1165: Refactoring changes to create a test runner option from passed flags, correct indentation and add package level comment for test
Documentation
Documentation was enhanced, including updates to the NativeTypes documentation regarding the cel tag, adding documentation for the optional library, and documenting the standard library functions/macros as part of the documentation string feature.
#1148: Update NativeTypes doc to reflect how to enable cel tag
#1155: Utilities for formatting and parsing documentation strings
#1156: Support for documentation and example strings in CEL environments
#1159: Document the standard library macros and functions
#1162: Document optional library and increase docs coverage
Build System
Configuration fixes were made for Bzlmod compatibility.
#1146: Bzlmod configuration fixes
Type System
Type formatting was updated to correctly handle type parameters.
#1154: Update type formatting for type params
v0.24.1Compare Source
Fixes
Full Changelog: google/cel-go@v0.24.0...v0.24.1
v0.24.0Compare Source
Support for subsetting CEL standard library and serialization of CEL environments to YAML.
CEL is an official Google product [#1122]
Features
Fixes
New Contributors
Full Changelog: google/cel-go@v0.23.2...v0.24.0
harvester/harvester (github.com/harvester/harvester)
v1.6.0Compare Source
Harvester v1.6.0 Release Notes
This release introduces several features, enhancements, and bug fixes that improve system quality and the overall user experience. The documentation is available at https://docs.harvesterhci.io/v1.6.
The Harvester team appreciates your contributions and looks forward to receiving feedback regarding this release.
Downloads
AMD64
Full ISO
💿 https://releases.rancher.com/harvester/v1.6.0/harvester-v1.6.0-amd64.iso
📁 https://releases.rancher.com/harvester/v1.6.0/harvester-v1.6.0-vmlinuz-amd64
📁 https://releases.rancher.com/harvester/v1.6.0/harvester-v1.6.0-initrd-amd64
📁 https://releases.rancher.com/harvester/v1.6.0/harvester-v1.6.0-rootfs-amd64.squashfs
✅ https://releases.rancher.com/harvester/v1.6.0/harvester-v1.6.0-amd64.sha512
📝 https://releases.rancher.com/harvester/v1.6.0/version.yaml
Net Install ISO
💿 https://releases.rancher.com/harvester/v1.6.0/harvester-v1.6.0-amd64-net-install.iso
📝 https://docs.harvesterhci.io/v1.6/install/net-install/
ARM64
💿 https://releases.rancher.com/harvester/v1.6.0/harvester-v1.6.0-arm64.iso
📁 https://releases.rancher.com/harvester/v1.6.0/harvester-v1.6.0-vmlinuz-arm64
📁 https://releases.rancher.com/harvester/v1.6.0/harvester-v1.6.0-initrd-arm64
📁 https://releases.rancher.com/harvester/v1.6.0/harvester-v1.6.0-rootfs-arm64.squashfs
✅ https://releases.rancher.com/harvester/v1.6.0/harvester-v1.6.0-arm64.sha512
📝 https://releases.rancher.com/harvester/v1.6.0/version-arm64.yaml
Installation
Harvester can be installed using the ISO image, a bootable USB drive, and PXE boot. A net install ISO image, which contains only the core OS components, is also now available. For more information, see the Installation section of the documentation.
Upgrades
Harvester only allows upgrades from supported versions. For more information about upgrade paths and procedures, see Upgrading Harvester.
Highlights
Experimental Features
Kube-OVN Operator
The
kubeovn-operatoradd-on is a tool for managing Kube-OVN as a secondary container network interface (CNI) on Harvester clusters. Kube-OVN provides advanced software-defined networking (SDN) capabilities such as virtual private cloud (VPC) and subnets for virtual machine workloads. When you enable the add-on, it deploys Kube-OVN to your Harvester cluster and creates the defaultConfigurationCRD, which defines the desired state of the Kube-OVN installation.Documentation | GitHub issue
Overlay Network
The Harvester network-controller leverages Kube-OVN to create an OVN-based virtualized network that supports advanced SDN capabilities such as VPCs and subnets for virtual machine workloads. An overlay network represents a virtual layer 2 switch that encapsulates and forwards traffic between virtual machines.
Documentation | GitHub issue
Virtual Private Cloud (VPC)
In Harvester, a VPC is a logical network container that you can use to manage and isolate subnets and traffic. Harvester provides a default VPC named
ovn-clusterand allows you to create custom VPCs. At a high level, VPC creation involves enabling the kubeovn-operator add-on, creating an overlay network and a subnet, and linking the two networks.The VPC implementation in Harvester v1.6.0 enables scalable, isolated L3 and L2 network structures across the cluster. Kube-OVN creates the VPC and its subnets, and manages all L3 logic (routing, NAT, VPC peering, and isolation). Harvester defines the overlay networks and provisions virtual machines that are connected to those overlay networks. This architecture provides a clear separation of concerns: Kube-OVN handles SDN, while Harvester handles virtualization.
Demo | Documentation | GitHub issue
VPC Network Connectivity
In Harvester v1.6.0, virtual machines can connect with external networks if they are part of a subnet within the default VPC (
ovn-cluster) and if thenatOutgoingsetting is enabled on that subnet. This setting enables network address translation (NAT) for all traffic leaving the subnet and heading to destinations outside of the VPC.Communication between virtual machines in different VPCs is also possible. To achieve this, you must configure a VPC peering connection and static routes that define how traffic is forwarded. However, peering is limited to custom VPCs. You cannot establish a peering connection between the default VPC (
ovn-cluster) and a custom VPC.Demo | Documentation | GitHub issue
Virtual Machine Isolation
Isolation between virtual machines is typically achieved using either VLANs (in traditional networks) or virtual switches (in Kube-OVN). If you want to isolate virtual machines within the same virtual switch network, you can use subnet access control lists (ACLs) and Kubernetes network policies to achieve the required micro-segmentation.
Demo | Documentation | GitHub issue
Fully Supported Features
Containerized Data Importer (CDI) Settings on the Harvester UI
Harvester uses CDI to manage virtual machine image operations for certain StorageClasses. Starting with v1.6.0, you can use the Harvester UI to configure CDI settings when creating or updating a StorageClass. Each field on the CDI Settings tab corresponds to an annotation that modifies a specific StorageClass parameter. With this enhancement, you can avoid direct changes to the storage profile or CDI, which may result in unexpected system behavior. Instead, allow the Harvester controller to synchronize and persist the storage profile configuration through the use of CDI annotations.
Demo | Documentation | GitHub issue
CPU and Memory Hotplug
Starting with Harvester v1.6.0, you can increase a virtual machine's CPU and memory resources while it is running. To use this feature, you must enable CPU and memory hotplug when you create the virtual machine. Once the virtual machine is created, you can add more CPU and memory resources at any time. Harvester automatically migrates the virtual machine to a node that has the necessary resources.
Demo | Documentation | GitHub issue
Live Migration Progress Monitoring
In Harvester v1.6.0, you can monitor the progress of virtual machine live migration directly from the Harvester UI. The Migration tab of the virtual machine details screen displays migration event information and real-time metrics such as remaining data and memory transfer rate. To view the information, you must ensure that the rancher-monitoring add-on is enabled.
Demo | Documentation | GitHub issue
Online Volume Expansion
Harvester v1.6.0 allows you to expand volumes that are in use, as long as the underlying storage provider supports the feature. This works for volumes that are attached to a running virtual machine, or that have persistent volume claims (PVCs) connected to a running pod in a guest cluster.
The Longhorn V1 Data Engine fully supports online volume expansion, but the V2 Data Engine currently does not support it. For third-party storage, Harvester blocks online volume expansion requests by default. To allow such requests, you must use the
csi-online-expand-validationsetting to validate the storage provider.Demo | Documentation | GitHub issues: 2811 and 7358
Third-Party Storage for Guest Clusters and Workloads
In Harvester v1.5.0, support for third-party storage is limited to provisioning of root and data volumes for virtual machines. Harvester v1.6.0 improves on this by also allowing you to provision guest clusters and their corresponding workloads with third-party storage solutions.
In your guest cluster, you must first create a new StorageClass that references the StorageClass you created in Harvester for the third-party storage solution. Then, you must create a PVC using this new StorageClass and mount it to your workload.
Demo | GitHub issues: 8075 and 8076
vm-import-controller Support for Third-Party Storage
When importing virtual machine images using the vm-import-controller add-on, you can now specify a third-party storage solution instead of using Longhorn by default. To use this functionality, simply add the
storageClassfield to theVirtualMachineImportspec and specify the StorageClass for the third-party storage solution. Harvester handles the import and storage placement without requiring you to perform additional manual steps.Demo | Documentation | GitHub Issue
Virtual Machine Migration Network
By default, Harvester migrates virtual machines over the built-in cluster network
mgmt, which is limited to one interface and is shared with cluster-wide workloads. If network segregation is required, you can configure a VM migration network to isolate migration traffic and improve bandwidth utilization.Configuring a VM migration network involves enabling the
vm-migration-networksetting and constructing a MultusNetworkAttachmentDefinitionCRD. Once the setting is applied, allvirt-handlerpods are restarted to apply the new network configuration.Demo | Documentation | GitHub issue
Features
Managemenu upon the unsupported Harvester clusters #8054Enhancements
vmstate-persistenceandlonghorn-staticStorageClasses should be treated as internal and not be used directly by users #8562promptRemove.confirmRelatedResourcemessage needs to be refactored #5280Bug Fixes
spec.domain.memory.guestfield is lost #8907Configuration
📅 Schedule: Branch creation - "after 10am on sunday" in timezone Asia/Taipei, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.