← Back to the front page
- Replicated now supports installing and managing single-node Kubernetes 1.9.3 appliances. We’ve written a guide to help you get started.
- The Kubernetes installation will work in airgapped, proxy and online environments.
- The installation scripts will install Docker, Kubernetes, Replicated and your application.
- We currently install Kubernetes 1.9.3.
- All persistence volumes (PVs) will be mounted as a
- For multi-node and more custom Kubernetes installations, Replicated can be installed in an existing Kubernetes cluster.
- Support bundle v2 has been updated to allow managing support definitions independently of your application yaml.
- By default, all installations will continue running the standard support bundle, reading the
support_cmd keys from the application yaml.
- The v2 support bundle will use support definitions from Replicated Console if any exist for your team. When using support definitions from console, files and commands specified within the application yaml are ignored.
- The new support bundle spec documentation is documented in the Help Center.
- Added support for anonymous LDAP binding when using the Replicated LDAP identity integration.
- User search DN is now optional for LDAP identity integration.
- When running on EC2, leaving the AWS_ACCESS_KEY/SECRET_ACCESS_KEY empty in the Snapshot configuration will now use IAM roles for authentication.
- The Swarm scheduler can be used with a proxy.
- Resolved an issue where the application would fail to start with
no such image error when application images were removed from docker.
- All known CVEs with patches have been fixed in Replicated Docker images.
- Fixed an issue on the native scheduler that could cause an error “image not found” if a container’s when condition is toggled from false to true during application startup.
- Resolved an issue that prevented
replicatedctl params import and
replicatedctl params export command from functioning properly when formatted with yaml.