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 k8s client library #188

Closed
aweiteka opened this issue Dec 20, 2016 · 4 comments
Closed

Use k8s client library #188

aweiteka opened this issue Dec 20, 2016 · 4 comments

Comments

@aweiteka
Copy link
Contributor

We need to extend our custom client to sign images from inside a build pod:

  • Use env vars KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT
  • Use token from /var/run/secrets/kubernetes.io/serviceaccount/token
  • Use CA from /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
  • Use namespace /var/run/secrets/kubernetes.io/serviceaccount/namespace

Our openshift client is a custom client. It would be much better to use the upstream k8s client. This shouldn't significantly increase the size of the project.

@mtrmac
Copy link
Collaborator

mtrmac commented Jan 7, 2017

I would dearly love to get rid of those 1000 lines; but using the OpenShift client did increase the size of the binary, by at least 50 MB if I remember correctly.

(That was an OpenShift client, using the OpenShift object types for the images etc, not a k8s client, though; perhaps that is something else entirely. It has also been more than 6 months since the original work, things might have changed.)

@aweiteka
Copy link
Contributor Author

Basic testing looks like using the k8s go-client adds 45MB.

$ ls -lh skopeo
-rwxr-xr-x. 1 root root 18M Jan 12 15:19 skopeo
$ ls -lh skopeo.kubeclient
-rwxr-xr-x. 1 root root 63M Jan 12 15:17 skopeo.kubeclient

giuseppe pushed a commit to giuseppe/image that referenced this issue Jan 24, 2017
vendor containers/image and OCI/image-spec
@rhatdan
Copy link
Member

rhatdan commented Apr 25, 2019

@aweiteka @mtrmac @vrothberg What is the state of this issue. It is two years old, can we close it?

@vrothberg
Copy link
Member

Let's close it. Feel free to reopen if the issue gets revived.

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

No branches or pull requests

4 participants