-
Notifications
You must be signed in to change notification settings - Fork 14
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
WIP: Use versioned_client #44
Conversation
Codecov Report
@@ Coverage Diff @@
## master #44 +/- ##
=======================================
- Coverage 50.91% 50% -0.92%
=======================================
Files 10 10
Lines 381 388 +7
Branches 46 48 +2
=======================================
Hits 194 194
- Misses 184 191 +7
Partials 3 3
Continue to review full report at Codecov.
|
Some version information:
And schedulerName only seems to be mentioned in the 1.7 spec.
|
With the latest txkube branch (LeastAuthority/txkube#132) this now fails differently:
It looks like the Heapster endpoints have been moved around. Notably, against Kubernetes 1.7 alpha whatever, |
The problem now seems unrelated to txkube. Instead, the issue is that the Heapster APIs no longer work the same way in 1.6 (and 1.7). However, I have been unable to determine how they do work... |
On 1.6 (and I would suppose earlier versions as well) the Heapster API (https://github.com/kubernetes/heapster/blob/master/docs/model.md) is accessible on the Heapster pod's port 8082... not published publically by default though (so, eg, you have to set up a port forward to get there). |
It ... looks a bit like ... Heapster removed the APIs Kubetop was based on. |
With some unrelated txkube hackery to make authentication work for my GKE cluster, this PR works against my 1.6.6 GKE cluster. |
This now seems to be working against k8s 1.6.3. It's still not working on my 1.6.7 cluster but that one appears not to have Heapster installed at all ... |
My attempt to have kubetop use versioned client from LeastAuthority/txkube#130
Unfortunately I still get the original error:
And I can't find any reference to
schedulerName
in the kubetop code (yet).