1.50.2
Bug Fixes
- Fixed a bug that caused KOTS to fail to detect private images when their domains are inaccessible during online installs.
- Fixed a bug that caused the set config command to fail if an appliction config has a required password value that was already set.
- Fixed a bug that caused the LocalImageName function to not require private images when
proxyPublicImagesis set. - Fixed a bug that could cause the secret used to pull private images to be removed during a KOTS Snapshot restore when multiple applications are installed.
- Fixed a bug that could cause Helm render on a chart deployed via the API to not be supported by the target Kubernetes cluster.
- Fixed a bug where private images would fail to kustomize when the experimental Helm rendering workflow beta for Helm charts was in use.
- Fixed a bug where private images would fail to deploy when both existing Helm Charts and the experimental Helm rendering workflow beta Helm charts were in use.
1.50.1
Bug Fixes
- Fixed a bug that caused KOTS in some cases to falsely identify a regular cluster as an OpenShift cluster.
- Fixed a bug that required the registry namespace to be provided in airgapped existing cluster installs and upgrades even though it’s an optional flag.
- Fixed a bug in the Admin Console license page where the “Sync License” button was misaligned.
1.50.0
New Features
-
Added the ability to opt-in to removing the MinIO object store dependency for
hostpathandnfssnapshot options for kURL embedded and existing cluster upgrades. The opt-in flags for this feature are the same as those introduced in KOTS 1.47.0 to remove KOTS’ dependency on Minio for application archives and support bundles. This feature leverages a new Velero plugin,local-volume-provider, to provide file system backups. If this opt-in is selected as part of the upgrade, KOTS will attempt to reconfigure Velero to use the new provider. Data is neither deleted, nor copied, from the filesystem during the migration and the migration process is irreversible. This option can also be specified for new KOTS installations on kURL embedded and existing clusters. When specified on new installs, MinIO will not be used by KOTS for filesystem snapshots.
NOTE: For existing offline clusters, customers will need to add this plugin to Velero prior to migration or installation. -
Added an output flag to KOTS CLI that provides a JSON formatted object to the following CLI commands: kots backup, restore, download, upload, upstream upgrade, and version.
-
Added command line completion to KOTS CLI.
Improvements
- Adjusted preflight statuses to more clearly reflect when these checks are bypassed by an Admin Console user.
- When some collectors are blocked by RBAC permissions, support-bundle and preflight CLI will now run for all permissible collectors, instead of terminating with an error, by default.
- Instance roles may now be used for authentication when using an Amazon Elastic Container Registry (ECR) repository.
Bug Fixes
- Fixed a bug that prevented installing an Airgap Package if the registry password contained a colon (":") character.
1.49.0
Improvements
- The kots pull and kots admin-console generate-manifests CLI commands will now save the manifests in the current working directory by default.
- Updated the warning message printed by the kots install command so that when KOTS fails to pull the application metadata it will mention that it could also cause the Admin Console to run without minimal role-based-access-control (RBAC) privileges, which may be required by the application.
- The
--kotsadm-namespaceflag is now optional in airgapped existing cluster installations and for the kots upstream upgrade CLI command. Its value can be concatenated to the--kotsadm-registryflag instead (such as in the kots install command). - Added better preflight check status on version history rows.
Bug Fixes
- Fixed a bug that caused the existing cluster workflow to show in an embedded environment if a user logged out before finishing app setup.
- Fixed a bug that made it possible to install the same license multiple times using automated installs.
- Fixed a bug that caused KOTS to not be able to detect the application spec (along with other KOTS kinds) if it’s part of a multi-yaml document, which caused status informers to be ignored in that case for example.
1.48.1
Bug Fixes
- Fixed a bug that caused application images to not be rewritten correctly in airgapped embedded clusters.
- Fixed a bug that caused some admin console installation flags to not be respected when applying the generated manifests manually due to a missing configmap.
- Fixed a bug that could cause some admin console installation flags to not be respected on consecutive installation attempts.
1.48.0
New Features
- Added image garbage collection for embedded clusters that will remove unused images from the embedded registry.
Improvements
- Added a new CLI command for generating Admin Console YAML manifests.
Bug Fixes
- Fixed a bug that could cause some custom objects to not be removed from the cluster when they are removed from the application.
- Fixed a bug that could cause private images hosted in GitHub’s Docker registry fail to pull.
- Fixed a bug that could cause Admin Console to become inaccessible if an application Config did not have any config groups defined.
1.47.3
Improvements
- Added support for uploading multiple files in the application config for repeatable config items.
- Added support to remove a file from the application config when using the file item type.
Bug Fixes
- Fixed a bug causing LicenseFieldValue template evaluations in the Config file to not render correctly.
- Fixed a bug that caused failed deployments to show as successful.
- Fixed a bug that prevented Helm charts from being deployed in multiple namespaces.
- Fixed a bug that caused the Admin Console to panic if the application did not contain a Config file.
- Fixed a bug that caused kots pull command to traverse the directory structure of the current working directory.
- Fixed a bug that caused some deployment status to show the wrong color and icon in the UI if preflight checks were skipped.
1.47.2
Bug Fixes
- Fixed a bug that could cause the namespace specified in a HelmChart spec to be ignored.
1.47.1
Improvements
- Upgraded Troubleshoot version to 0.13.3 which supports the ConfigMap collector and analyzer.
kots get appsCLI command displays currently deployed application version label.
Bug Fixes
- Fixed a bug where the
reset-tlscommand would not restart the kurl-proxy-kotsadm pod. - Fixed a bug where using the
--ensure-rbac=falseflag with install and upgrade commands would still attempt to modify RBAC objects. - Fixed a bug where a deployment would fail if the same resource is included in different Helm charts.
1.47.0
New Features
- Added the ability to opt-in to removing the MinIO object store dependency for KOTS for kURL embedded and existing cluster upgrades. If this opt-in is selected as part of the upgrade, KOTS will migrate all application archives and support bundles to a blob/filesystem that is part of the new KOTS Admin Console statefulset. The migration process is irreversible. This option is also available for new KOTS installs on kURL embedded and existing clusters. When specified on new installs, MinIO will not be used by KOTS for application archive or support bundle storage.
- Added a config option for repeatable items. This allows for more than one value to be provided under a single config item. The config item will target a YAML array or YAML file, which will be duplicated and rendered for as many values as are provided.
- Added experimental support for a new Helm rendering workflow that supports hook and hook weight for v3 Helm charts. The new workflow applies to the following hooks: pre-install, post-install, pre-upgrade, post-upgrade. This feature is experimental and only available to vendors who have requested access.
Improvements
- Added default analyzer for Longhorn.