[ncc-services-wg] RIPE NCC and the Cloud: Draft Principles, Requirements and Strategy Framework

>> maybe i see it as more 'extending' rather than 'moving'. visions of
>> slimy pseudopods :)
> All engineering metaphors are best explained in grotesque terms :)

and i get no credit for the k8s pun?  sigh.  :)

yes, we use k8s in one of my $dayjobs.  it is far more architecturally
organized/structured than, e.g., openstack.  as with many very powerful
tools, you can make as complex a mess as you want; and it takes mature
skills not to do so.  but one can deploy on maas, which is really nice
in this case.  i know this is a violation of mailing list rules; but i
do not understand the ncc's needs in sufficient depth to have a valid
opinion if k8s is an appropriate tool here.

randy