v0.11.0-beta.2
Pre-release
Pre-release
neonforgedevbot
released this
05 Apr 02:35
·
317 commits
to master
since this release
PRERELEASE
Component | Version |
---|---|
NEONKUBE | $<neonkube.version> |
KUBERNETES | $<kubernetes.version> |
This release is not a production ready and is intended to introduce new features and fixes.
This release is suitable for testing purposes but be advised that prerelease features may see
breaking changes in future releases or be removed completely.
The NeonDESKTOP cluster is having trouble stabilizing due to ephemeral storage constraints.
We'll have a look at this for the next release.
Release Taxonomy
Release Type | Usage | Description |
---|---|---|
ALPHA | private testing | Used internally and potentially provided to specific users for testing purposes |
BETA | public testing | Early release with no guarantee that we won't make breaking changes before release |
PREVIEW | public testing | More stable early release. Release breaking changes are less likely than BETA |
RC | release candidate | Nearly ready for a stable production release |
STABLE | production | Ready for production |
Release documentation: https://docs.neonforge.com/docs/neonkube
Details
- [bug] #437 On-premise cluster/node identification
- [bug] #1890 neon-cli: ArgumentOutOfRangeException in Windows Terminal
- [bug] desktop cluster setup: Failure adding virtual Ethernet switch
- [bug] #1896
neon cluster delete --force
doesn't delete hyper-v cluster in non-admin mode - [bug] NeonDESKTOP wizard window need to be vertically centered
- [bug] NeonDESKTOP setup configures cluster-id early so cluster delete will work
- [bug] NeonDESKTOP setup cancellation improvements
- [bug] NeonDESKTOP cluster TLS certificate renewal needs to happen in a setup step action
- [bug] NeonDESKTOP SSH password set to sysadmin0000
- NeonDesktop now requires Windows machine with 32GiB RAM for better stablility. We intended to
include this change in v0.11.0-beta.1, but it didn't make it in. - Upgrade: Podman v3.4.2 --> v5.0.0
- HypervisorOptions.NamePrefix: Now uses "[none]" to indicate that no prefix is to be added to on-premise cluster VMs.
- Increased cluster deployment operation timeout from 10 --> 15 minutes
- Increase lower bound of node host OS ephemeral IPv4 port range: [10000...65535] --> [16000...65535]