-
Notifications
You must be signed in to change notification settings - Fork 415
Calico with Mesos and Kubernetes integrated #1521
Conversation
Enabled calico support fr k8s
Setting this environment variable causes the libprocess library that Mesos uses to overwrite all IP information for a process spawned by the Mesos agent.
…ucture into feature/mkc-combo-working
Fixes #1514 |
@@ -0,0 +1,138 @@ | |||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this was probably checked in accidentally
@Zogg Awesome job! Do we need to update/create any documentation around this? |
@@ -198,8 +198,10 @@ resource "google_compute_instance" "mi-worker-nodes" { | |||
} | |||
} | |||
|
|||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can probably just drop this commit
@Zogg Also, have you been able to test with more recent versions of Mesos and Marathon? Marathon is at v1.1.1, and they recommend Mesos 0.28.0 to go with it. |
A lot of testing has been done with various mesos/marathon/calico/kube versions. The exact versions that will go into 1.2 will be resolved in respective component PRs. |
After a long period, with issues resolved, we finally have the Calico and Mesos and Kubernetes working together.
Champagne popping sound
Calico: 0.15.0
Kubernetes: 1.2.0
Mesos: 0.27.0
Marathon: 1.0.0_RC1
Components version upgrades are to be supplied through their respective PRs.