2.0.5

• Allow YAML formatted cluster dumps
• Add ocne info subcommand to display build and version information as well as some options that are difficult to discover
• Add more supported compute shapes for OCI
• Allow customization of ignition provider and kernel arguments during ocne image create
• Fixed various minor issues in cluster dump and analyze
• Bump some dependencies
• Allow automatic installation of the community catalog at ArtifactHub.io
• Fixed an issue where updating an application with no customizations would fail.

2.0.4

• Install Catalog and UI with custom container image registry when using the "none" provider
• Fixed an issue where Flannel-based pod networking did not function with a default oci provider configuration
• The oci provider can now automatically configure OCI-CCM
• Deleting clusters that use the oci provider is now synchronous

2.0.3

• Clean up some stale code
• Ensure that the OCI instance metadata service is set in no_proxy for the oci provider
• Fix issue with configuration precedence where some configuration file values would take precedence over the CLI
• Relax restrictions on cluster version when creating images
• Enable the use of custom OCK image tags
• Improve the keepalived liveness probe to tolerate high latency responses from kube-apiserver.

2.0.2

• Added support for additional ostree transports for the cluster update service
• Addressed some cases in cluster dumps when some output was not displayed when redaction is enabled
• It is now possible to completely reset the values when updating an application
• Fixed an issue where CLI and cluster config file argument priority was inverted, causing config files to win over CLI arguments

2.0.1

The cluster console can now automatically change the filesystem root to the host filesystem. It also accepts a double dash argument - "--" - to indicate that command arguments are complete. Any arguments after the double dash are interpreted as a command to execute on the cluster node.

The syntax for specifying ostree container image references has been relaxed. It is now possible to specify a container image registry without including a transport. If no transport is specified, "ostree-unverified-registry" is used.