Commit 9522e0ef authored by Dr. Stefan Schimanski's avatar Dr. Stefan Schimanski

contrib/mesos/scheduler: create nodes with ready condition

The current kube-ui version (compare https://github.com/kubernetes/kube-ui/pull/37/files#r46950087) assumes that the first node condition is the Ready condition. This PR works around this by enforcing the Ready condition to be the first one. A parallel PR against kube-ui is on the way.
parent 41cb3d6a
......@@ -21,13 +21,13 @@ import (
"reflect"
"strconv"
"strings"
"time"
log "github.com/golang/glog"
mesos "github.com/mesos/mesos-go/mesosproto"
"k8s.io/kubernetes/pkg/api"
"k8s.io/kubernetes/pkg/api/errors"
"k8s.io/kubernetes/pkg/api/unversioned"
client "k8s.io/kubernetes/pkg/client/unversioned"
"k8s.io/kubernetes/pkg/util/validation"
)
......@@ -55,6 +55,19 @@ func Create(
},
Status: api.NodeStatus{
Phase: api.NodePending,
// WORKAROUND(sttts): make sure that the Ready condition is the
// first one. The kube-ui v3 depends on this assumption.
// TODO(sttts): remove this workaround when kube-ui v4 is used or we
// merge this with the statusupdate in the controller manager.
Conditions: []api.NodeCondition{
{
Type: api.NodeReady,
Status: api.ConditionTrue,
Reason: slaveReadyReason,
Message: slaveReadyMessage,
LastHeartbeatTime: unversioned.Now(),
},
},
},
}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment