KuberDock and Docker Blog

KuberDock 1.5.0 and new KuberDock plugins released

KuberDock 1.5.0 and new KuberDock plugins released

We are pleased to announce that after a month of private beta testing, KuberDock version 1.5.0 is now available to everybody. This latest version is the result of work done by our development team and embodies further improvements to the product and new features added based on our customers’ requests.

KuberDock is now more reliable and stable than ever due to bug fixes described below.

To upgrade KuberDock, run kuberdock-upgrade at master. Please note that we do not support automated upgrade from 1.4.0 to 1.5.0 for AWS instances - in case you need it, please contact our support.

To upgrade KuberDock CLI just run yum update kuberdock-cli.

To upgrade KuberDock plugin for shared hosting panels — cPanel, Plesk and DirectAdmin — run bash ./kcli-deploy.sh --upgrade.

To install KuberDock plugin for Plesk, follow our simple installation guide. To install it for DirectAdmin refer its installation instructions.

To upgrade KuberDock plugin for WHMCS go by the Update WHMCS Addon guideline. 

Should you encounter any problems with the upgrade or have any questions, comments or suggetions, please contact our support team at helpdesk.cloudlinux.com: KuberDock department. We’d be more than happy to help you.

Key Improvements

 

  • KuberDock now upgraded to Docker 1.12 version for better performance, stability, security, and reliability.

  • Starting from version 1.5.0, KuberDock networking is now based on the Calico solution for networking (see the Project Calico homepage). With almost no overheads, it produces immediate advantages such as improved scalability, more reliable and flexible isolation at pod and cluster levels, and out-of-the-box support of the most popular public cloud platforms —AWS, GCE and DigitalOcean. It also simplified KuberDock maintenance due to global community involvement in the solution development and stabilization, etc.

  • Working on Shared IP feature improvement, we have added CloudFlare as the available DNS provider. Also, the ability to specify in YAML custom hostname part of the domain name has been implemented for Predefined Applications.

  • ZFS has been added as an alternative Local Storage backend. This file system natively manages both disks and volumes similarly to RAID technologies, protects data against disk errors caused by bugs in the firmware, malfunctions of the hardware or even bad cables, corrects any error using redundant data, offers a sophisticated layered caching, etc. With this, KuberDock now armed with file system consistent backups based on ZFS. It can be selected via the flag --zfs of the deploy.sh script. It is default Local Storage backend when deploying in AWS. Its default settings have been adjusted to optimize overall Input/Output performance.

 

Other Improvements

 

  • We have updated our EULA. Please read it carefully at http://kuberdock.com/LICENSE.TXT

  • Improved IP pool page and pagination on it, so that now you can see all IPs in a pool with more than 256 IPs.

  • Additional verification method is added - it allows checking if the cluster has a particular node with a particular Kube Type before billing system will send an invoice to avoid situations when a customer has paid for application but can’t start it due to inability to deploy application.

  • One more controlled variable — AWS_EBS_DEFAULT_SIZE — has been introduced in the file config-default.sh. It prescribes initial size (in GB) of EBS volume for persistent storage when a node is created and the default increment when the storage is expanded. Its initial value is 20 GB.

  • Ability to resize Persistent Volumes based on Local Storage has been provided. This may be done via execution of Python script manage.py. The resizing is also done automatically as a result of application package change.

  • From now, cluster health-check is automatically run not only before cluster upgrade but after its successful completion as well. This guarantees service and users’ pods have no issues after the upgrade.

  • Improved UI for Add Predefined Application page - now text area has validation and line number for more comfortable work.

  • Added validation to Billing setting page so that KuberDock will try to check if billing setting works properly to avoid problems.

  • KuberDock internal pods now cannot be edited and we hid all buttons that allow editing of internal pods.

  • If the admin tries to create a user with the exact email that already exists in WHMCS and did before in KuberDock, then KuberDock will propose to restore it instead of creating a new user. Read more in the documentation here.

  • Added a new type of notifications in the left bottom of the page which is called “warning” and has an orange color.

  • Once user edits a Predefined Application, KuberDock will forbid ability to switch application package.

  • In YAML files we rename option “domain” to “baseDomain” to avoid confusion. Read more here.

  • Improved UI on the second step of pod creation process for clusters on AWS. Added ability to set a maximum kubes quantity for Trial users. Read more about it here. Added hint to the second step of pod creation process for Domain usage instead of IP.

  • Access endpoints now have more relevant notions in all KuberDock interface for end users and admins. We have also updated notions for a cluster on AWS to make it clearer.

  • Almost all node ports are closed by default for security reasons, however, now several console commands to manage accessibility of the ports when necessary have been made available.

  • Intra-cluster Domain Name Service has been made more reliable and robust.

  • From now, Linux default limitations imposed on asynchronous events are automatically leveled up to allow creation of more than 24 DB containers (particularly MySQL ones) per node.

 

Fixes

 

  • Notify earlier about the wrong or undefined timezone.

  • Fixed unfriendly error message shown when the user tries to run custom container from Docker Hub.

  • Fixed a bug that made customization and branding disappear when you update KuberDock.  From now on, KuberDock customizations persist and will not be reset during KuberDock update.

  • Fixed a bug with positioning buttons “Next”, “Back” and “Cancel” on the container creation pages.

  • Fixed a bug when customer edits pod and deletes public IP from it then public IP still exists  for this pod after saving changes.

  • Fixed a bug in the user interface with long DNS names in case of AWS cluster.

  • The bug that caused deadlocks during unclosed DB transactions while upgrading KuberDock has been fixed.

  • Failures of Ceph pool creation during KuberDock deployment are now handled correctly.

  • A pod might remain of Running status even when the creation of its Ceph-based Persistent Volume had failed. The situation has been corrected.

  • The bug when trailing slash in a path might cause malfunction of the name resolving has been fixed.

  • Fixed a bug when a Predefined Application couldn't start normally when a customer buys few applications at once.

  • Fixed a bug when pods cannot sometimes restart after edit pod process.

  • Fixed a bug when in some cases internal Kube Type used for Internal services available for the customers on the last step of pod creation process.

  • Fixed a bug when a trial user cannot change kubes quantity for the container during the editing process.

  • Fixed a bug when a customer tries to buy Predefined Application and got error 500 if there is a free IP in IP pool.

  • Fixed a bug which sometimes made it impossible to create user form KuberDock UI.

  • Fixed a bug when after creating a new user with some symbols or number in fields First Name, Last Name, Middle Initials or Email KuberDock will not save it properly.

  • Fixed a bug when a user switches Predefined Application package with different size of persistent storage and the size did not actually change.

  • Fixed a bug with new python-cerberus not working with IPv4 validating.

  • Fixed a bug when second KuberDock node status becomes Trouble after deploying on AWS.

  • Fixed a problem when a YAML specification is saved even if validation errors exist.

  • Fixed a bug when the administrator is not able to view all IPs in added IP subnet.

  • Fixed a bug with a user authentication through token2 when a customer buys a Predefined Application.

  • Fixed wrong error message that is shown when node goes down.

  • Fixed unexpected password request in AWS deploy.

 

KuberDock WHMCS plugin 1.1.0 changelog

 

Bugfixes

 

  • Fixed an error when Plugin hooks do not run for newly installed WHMCS.

  • Fixed deleting the billable item when a pod from KuberDock is deleted.

  • Fixed an error when the module does not work without specified date.timezone.

  • Fixed user undelete issues.

  • Fixed Predefined Application zero price error in function setAttributes().

  • Fixed wrong First Deposit in the cart.

 

KuberDock plugin for control panels 1.2-3 changelog

 

Improvements

 

  • Updated EULA: You can find new EULA on the server where plugin is installed and the path is: /usr/share/kuberdock-plugin/LICENSE

  • DirectAdmin: Added a new tab with available Predefined Applications for the user.

 

Bugfixes

 

  • Plesk: Fixed an error that appears when a login contains a dot in the name.

  • Plesk: Fixed a bug with excessive tabs.

Topic: KuberDock & Docker Blog , Tags: #docker,

1180 people viewed this

Comments

 
No comments yet

Leave your comment

Guest, Tuesday, 26 September 2017

Captcha Image