(1)I am searching for a way to assign a pod to a specific node(machine). I think the selector and label cannot meet my requirement right? Does Kubernetes support this feature right now? Because in Fleet I can specify the metadata of a node(machine) and match it with services.

(2)Another question is that if I use a service to assemble some sorts of pods, like this
wordpress name=wordpress 172.17.2.0 22222

and through api I can see such result
{
"id": "wordpress",
"creationTimestamp": "2014-11-12T05:36:43-05:00",
"selfLink": "/api/v1beta1/services/wordpress",
"resourceVersion": 1797,
"namespace": "pod",
"port": 22222,
"protocol": "TCP",
"selector": {
"name": "wordpress"
},
"containerPort": 11111,
"portalIP": "172.17.2.0"
}
As it implies this service has a internal portal IP and port, my question is that
(1) Is there anyway I can access this service through public network? Or this service can only be used by other pods within the internal network
(2) So service basically is just made up of some key-values stored in etcd and updated regularly?

Questions are a little dumb because I am pretty new to this and also have limited Linux and network background. Really appreciate someone who can help me with such problem.