install error

[bay1ts]

I want to achieve similar kubectl drain function, when I refer to the source code, I hit the following error in function "evictPods":

../pkg/k8s/K8S.go:190: cannot use "k8s.io/apimachinery/pkg/apis/meta/v1".TypeMeta literal (type "k8s.io/apimachinery/pkg/apis/meta/v1".TypeMeta) as type "k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/apis/meta/v1".TypeMeta in field value
../pkg/k8s/K8S.go:194: cannot use "k8s.io/apimachinery/pkg/apis/meta/v1".ObjectMeta literal (type "k8s.io/apimachinery/pkg/apis/meta/v1".ObjectMeta) as type "k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/apis/meta/v1".ObjectMeta in field value
../pkg/k8s/K8S.go:195: cannot use deleteOptions (type *"k8s.io/apimachinery/pkg/apis/meta/v1".DeleteOptions) as type *"k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/apis/meta/v1".DeleteOptions in field value
../pkg/k8s/K8S.go:198: cannot use eviction (type *policy.Eviction) as type *"acp_node/vendor/k8s.io/client-go/pkg/apis/policy/v1beta1".Eviction in argument to clientSet.Policy().Evictions(eviction.ObjectMeta.Namespace).Evict

[ericchiang]

Can you describe how you installed client-go? Did you use any of the instructions in https://github.com/kubernetes/client-go/blob/master/INSTALL.md ?

[beeradb]

I have the same issue. Using the code from https://github.com/kubernetes/client-go/blob/release-4.0/examples/in-cluster-client-configuration/main.go with dep for dependency management.

Running dep init after copying the code results in a successful initialization. The final line of the output is:

Locking in v4.0.0 (d92e849) for direct dep k8s.io/client-go

Trying to run the code results in the following error:

# github.com/org/project/vendor/k8s.io/client-go/tools/clientcmd/api
vendor/k8s.io/client-go/tools/clientcmd/api/register.go:35:11: cannot use Config literal (type *Config) as type runtime.Object in argument to scheme.AddKnownTypes:
	*Config does not implement runtime.Object (missing DeepCopyObject method)
# github.com/org/project/vendor/k8s.io/client-go/pkg/apis/admissionregistration
vendor/k8s.io/client-go/pkg/apis/admissionregistration/register.go:47:29: cannot use InitializerConfiguration literal (type *InitializerConfiguration) as type runtime.Object in argument to scheme.AddKnownTypes:
	*InitializerConfiguration does not implement runtime.Object (missing DeepCopyObject method)
vendor/k8s.io/client-go/pkg/apis/admissionregistration/register.go:48:33: cannot use InitializerConfigurationList literal (type *InitializerConfigurationList) as type runtime.Object in argument to scheme.AddKnownTypes:
	*InitializerConfigurationList does not implement runtime.Object (missing DeepCopyObject method)

<truncated but very long list of similar errors here>
vendor/k8s.io/client-go/pkg/api/register.go:85:24: too many errors

I'm happy to provide the rest of the output from above as well as the Gopkg.lock file if that would be beneficial.

[wangweihong]

met same errros too. My kubernetes's source code version is 1.7.3. client-go is v4.0.0. apimachinery is release-1.7.

[beeradb]

I was able to get the example from #293 (comment) to run by using Glide.

[jlovero-isp]

I'm seeing the similar errors to @beeradb after trying to run the code examples when I pull dependencies using dep. I used the instructions in INSTALL.md to lock the client-go library to v4.0.0. Any attempts to run either the code examples or code of my own results in a long list of errors that take the following form:

cannot use T literal (type *T) as type runtime.Object in argument to scheme.AddKnownTypes:
	*T does not implement runtime.Object (missing DeepCopyObject method)

Where T is a type.

Edit:
I switched to Glide and it works without any other changes. ¯_(ツ)_/¯

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close