Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use new k8s go client #2659

Merged
merged 7 commits into from
Jul 3, 2017
Merged

Use new k8s go client #2659

merged 7 commits into from
Jul 3, 2017

Conversation

2opremio
Copy link
Contributor

@2opremio 2opremio commented Jun 28, 2017

This namely involved importing new libraries and using the new Clientset.

Changes worth mentioning:

  • The new kubernetes library doesn't provide StoreToLister wrappers, so now I am doing the casting directly.
  • Deleting the pods and getting their logs is done in a cleaner way (using the
    Clientset instead of the lower-level RESTclient).
  • HostNetwork is now inlined in the pod spec

After merging this PR we should probably create a new one to replace the raw cache.Stores by the newer SharedIndexInformer. This will allow us to:

  • Get rid of EventStore (we can set event handlers directly with the Informer interface)
  • Stop using raw, low-level cache.Stores and castings (we can create listers like PodLister using the indexer).

TODO:

  • Update and successfully run unit tests
  • Run in dev to check nothing broke
  • Remove old vendored libraries

@2opremio 2opremio changed the title [WIP] Use new k8s go client Use new k8s go client Jun 29, 2017
@2opremio 2opremio requested a review from ekimekim June 29, 2017 10:16
@2opremio 2opremio force-pushed the use-new-k8s-go-client branch from 78fa6c7 to e3bc6fe Compare June 30, 2017 08:23
@2opremio
Copy link
Contributor Author

Rebased due to conflict in vendor/manifest

@2opremio
Copy link
Contributor Author

Tests started failing after I rebased:

>>> Test ./330_process_edge_test.sh finished after 178.0 secs with error: exit status 1
Error response from daemon: failed deleting network: legacy plugin: Post http://%2Frun%2Fdocker%2Fplugins%2Fweavemesh.sock/Plugin.Activate: dial unix /run/docker/plugins/weavemesh.sock: connect: connection refused

@ekimekim
Copy link
Contributor

ekimekim commented Jul 1, 2017

It's failed with 3 different error messages across 3 runs. And I can't run the integration tests locally, apparently they use GCE and I need creds.

@rade
Copy link
Member

rade commented Jul 2, 2017

And I can't run the integration tests locally, apparently they use GCE and I need creds.

You should be able to run the tests against local VMs. If that is not working, please raise an issue and fix it.

Alfonso Acosta added 7 commits July 3, 2017 20:20
This namely involved importing new libraries and using the new Clientset.

Changes worth mentioning:

* The new kubernetes library doesn't provide StoreToLister wrappers, so now I am going the casting directly.
* Deleting the pods and getting their logs is done in a cleaner way (using the
  Clientset instead of the lower-level RESTclient).
@2opremio 2opremio force-pushed the use-new-k8s-go-client branch from e3bc6fe to 93b0bc8 Compare July 3, 2017 20:20
@2opremio
Copy link
Contributor Author

2opremio commented Jul 3, 2017

Rebased again to see if the error was transient (no other PR seems to be suffering from this)

@2opremio 2opremio merged commit 6c03540 into master Jul 3, 2017
@2opremio 2opremio deleted the use-new-k8s-go-client branch July 3, 2017 21:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants