Fwd: [kubernetes-announce] Incompatible changes coming: Services v2, Namespaces, new API objects

[Imesh Gunaratne <im...@apache.org>]

FYI

---------- Forwarded message ----------
From: 'Tim Hockin' via kubernetes-announce <
kubernetes-announce@googlegroups.com>
Date: Tue, Oct 14, 2014 at 5:59 AM
Subject: [kubernetes-announce] Incompatible changes coming: Services v2,
Namespaces, new API objects
To: kubernetes-announce@googlegroups.com


Hi all,

A week and a half ago, I warned you all of a pending incompatible
change (
https://groups.google.com/forum/#!topic/kubernetes-announce/oO7Bs_c16lI)
in Kubernetes.  This message is a revision.

There are a number of incompatible changes that have been brewing in
Kubernetes, and we've decided that it's better to rip the band-aid off
all at once and commit them all together.  We intend to get all of the
below changes committed in one day, hopefully this week.  I will send
an announcement here before we start the process of committing them
and again when we are done.

Any pods, replication controllers, or services that you have running
in your clusters will have to be destroyed and re-created.  We
apologize for any inconvenience, and we appreciate your understanding
as we try to keep things moving forward in Kubernetes.

Summary of changes:

1) IP-per-service:
https://github.com/GoogleCloudPlatform/kubernetes/pull/1402

This change will almost completely eliminate the problem of
coordinating shared ports in Kubernetes.  Every Service will now get
its own virtual IP address, which means it can use any port you want.
For details about how this works, please see the above-linked
pull-request.  Because of this, the environment variable
"SERVICE_HOST" will no longer work.  A few weeks ago we introduced
per-Service variables to replace SERVICE_HOST.  If you have a service
named "foo", you can use FOO_SERVICE_HOST, which will contain the
right IP after this change, or you can use the Docker-links style
variables, which will continue to be supported.


2) Namespaces:  https://github.com/GoogleCloudPlatform/kubernetes/pull/1564

This change represents one of the final pieces of the namespace
feature, which provides the mechanism to subdivide your Kubernetes
cluster into a set of logically scoped units.  Each namespace manages
its own set of pods, replication controllers, and services.  If you're
not ready to use namespaces yet, don't worry - all of the content you
create in your cluster will just reside in the "default" namespace.


3) BoundPods:  https://github.com/GoogleCloudPlatform/kubernetes/pull/1662

This change is part of the introduction of the v1beta3 API - a fairly
substantial set of changes to re-organize how we describe the
Kubernetes system.  If you use the API directly, you might want to
read up on the changes in this API version - there are quite a few.


We're pretty excited to be getting these changes in - we really
believe they make Kubernetes a better system to use, and we think you
will agree.  If something doesn't work for you, or isn't clear, please
file an issue (https://github.com/GoogleCloudPlatform/kubernetes/issues/new
),
find us on IRC, or drop me a note directly, and we will sort it out.


Tim

--
You received this message because you are subscribed to the Google Groups
"kubernetes-announce" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to kubernetes-announce+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/kubernetes-announce/CAO_RewYbo4ASzO9gLfrPfQRbQOrcFgm5_mwsXkbOhgLn51QeAA%40mail.gmail.com
.
For more options, visit https://groups.google.com/d/optout.



-- 
Imesh Gunaratne

Technical Lead, WSO2
Committer & PMC Member, Apache Stratos