[magnum][kubernetes] Train release updates

feilong feilong at catalyst.net.nz
Thu Oct 24 08:27:23 UTC 2019


Thanks Tim. That's good point. Will do when we release the Magnum 9.1.0
version. Cheers.


On 24/10/19 7:11 PM, Tim Bell wrote:
> Feilong,
>
> Great to see all of these improvements getting into the release.
>
> Would it be possible to add these to the release highlights
> documentation at https://releases.openstack.org/train/highlights.html ?
>
> Tim
>
>> On 24 Oct 2019, at 07:56, feilong <feilong at catalyst.net.nz
>> <mailto:feilong at catalyst.net.nz>> wrote:
>>
>> Hi all,
>>
>> Glad to see the Train just released. I'd like to take this opportunity
>> to highlight some cool features Magnum team have done in this cycle.
>> Please feel free to pop up at #openstack-containers for any feedback.
>> Thank you.
>>
>> 1. Fedora CoreOS driver
>>
>> Finally we get this done in this cycle which is quite important and
>> urgent. Because the Fedora Atomic will be end of life soon (at the end
>> of this Nov?). Now with stable/train, user can create k8s cluster based
>> on Fedora CoreOS image. We're welcome for any feedback about this.
>>
>> 2. Node group
>>
>> This is a quite large feature, thanks for the great work from CERN team
>> and StackHPC. With this feature, user can create different node groups
>> with different specs.
>>
>> 3. Rolling upgrade
>>
>> Now user can do rolling upgrade for both k8s version and the node
>> operating system without downtime, it's a quite important feature.
>>
>> 4. Auto healing
>>
>> With auto healing feature, a small service will be deployed on k8s
>> cluster to monitor the health status of the cluster and replace broken
>> node when failure detected.
>>
>> 5. Volume based k8s nodes
>>
>> Now user can create a Kubernetes cluster with nodes based on volume and
>> the volume type is configurable. User can even set the volume type of
>> etcd volume which is very useful for cloud providers who want to use SSD
>> for etcd and k8s nodes.
>>
>> 6. Private cluster
>>
>> As a security best practice, isolating Kubernetes clusters from Internet
>> access is one of the most desired features for enterprise users. Now
>> user has the flexibility to create a private cluster by default, only
>> allow the API exposed on Internet or fully opened.
>>
>> -- 
>> Cheers & Best regards,
>> Feilong Wang (王飞龙)
>> ------------------------------------------------------
>> Senior Cloud Software Engineer
>> Tel: +64-48032246
>> Email: flwang at catalyst.net.nz <mailto:flwang at catalyst.net.nz>
>> Catalyst IT Limited
>> Level 6, Catalyst House, 150 Willis Street, Wellington
>> ------------------------------------------------------
>>
>>
>
-- 
Cheers & Best regards,
Feilong Wang (王飞龙)
------------------------------------------------------
Senior Cloud Software Engineer
Tel: +64-48032246
Email: flwang at catalyst.net.nz
Catalyst IT Limited
Level 6, Catalyst House, 150 Willis Street, Wellington
------------------------------------------------------ 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20191024/47890913/attachment.html>


More information about the openstack-discuss mailing list