tsloughter / kuberl Goto Github PK

View Code? Open in Web Editor NEW

54.0 6.0 8.0 656 KB

Erlang Kubernetes client

Shell 0.04% Erlang 99.52% Makefile 0.04% Nix 0.40%

erlang kubernetes kubernetes-controller

kuberl's Introduction

Erlang Kubernetes client

Erlang client for Kubernetes 1.16 generated through Swagger.

Watch Behaviour

The behaviour kuberl_watch starts a process to stream the results of a watch requests and calls the callback handle_event with the notification type (added, modified, deleted) and the resource object.

Using the API

Configuration

The API server endpoint and key can be configured in environment configuration variables:

[{kuberl, [{api_key, <<"... bearer token ...">>},
           {host, "https://x.x.x.x"}]}].

This will set a default configuration used if none is passed to API requests.

A new configuration can be created with functions in kuberl:

Cfg = kuberl:cfg_with_bearer_token(kuberl:cfg_with_host("https://x.x.x.x"), <<"... bearer token ...">>),
kuberl_core_api:get_api_versions(ctx:background(), #{cfg => Cfg}).

Optionally the environment config can be overridden at runtime:

kuberl:set_default_cfg(Cfg).

Update Generated Code

Without Nix

With swagger-codegen built under ../swagger-codegen the script in the bin directory can be used to update the generated Erlang modules:

bin/update-generated-code.sh

This script will generate the code to a temporary directory under /tmp and then copy only the modules to gen/.

With Nix

Install Nix, direnv, and lorri.

# Run the lorri daemon
lorri daemon

# or watch this directory (once)
lorri watch # --once

# load the environment
direnv allow

# generate the code
kuberl_gen

kuberl_gen will generate the code to a temporary directory under /tmp and then copy only the modules to gen/.

kuberl's People

Contributors

Stargazers

Watchers

Forkers

nilium vasu-dasari pedro-gutierrez yurrriq laymer ringtail huiqing lincolnbryant

kuberl's Issues

Any plans to update?

I'm interested to use this with k8s >=1.15

Authentication header missing from request

I've configured sys.config as per the README, but for some reason, my requests have no Authentication header, so I keep getting 401'd. Please advise.

28> kuberl_core_api:get_api_versions(ctx:background(), #{cfg => kuberl:new_cfg()}).
(<0.256.0>) call hackney:request(get,<<"https://api.mycluster.fake/api">>,[{<<"Content-Type">>,<<"application/json">>}],<<"[]">>,[{ssl_options,[{server_name_indication,disable}]}])
(<0.256.0>) call hackney:request(get,{hackney_url,hackney_ssl,https,<<"api.mycluster.fake">>,<<"/api">>,
             <<"/api">>,<<>>,<<>>,"api.mycluster.fake",443,<<>>,<<>>},[{<<"Content-Type">>,<<"application/json">>}],<<"[]">>,[{ssl_options,[{server_name_indication,disable}]}])
{error,#{apiVersion => <<"v1">>,code => 401,kind => <<"Status">>,
         message => <<"Unauthorized">>,metadata => #{},
         reason => <<"Unauthorized">>,status => <<"Failure">>},
       #{headers =>
             [{<<"Content-Type">>,<<"application/json">>},
              {<<"Www-Authenticate">>,
               <<"Basic realm=\"kubernetes-master\"">>},
              {<<"Date">>,<<"Tue, 29 May 2018 21:28:52 GMT">>},
              {<<"Content-Length">>,<<"129">>}],
         status => 401}}

Figure out resourceVersion

I don't think it is currently using resourceVersion correctly, at least in cases like the example which lists all pods for all namespaces.

Without a resourceVersion it will fetch all pods again on every reconnect after a timeout. But as far as I can tell resourceVersion is about the individual resource, like a single pod, and isn't clear if it can be used as the example currently is where the resourceVersion of last pod decoded is used as the version for the next request.

401: Unauthorized error

Hi,

Thanks for a wonderful package kuberl. I was thinking of writing this kind of project along this lines. Maybe I can help in this project as time goes by.

For now, I am trying to execute the example code highlighted in README.md. The following might not be a bug, probably the way I am using it.

I started minikube from my Mac OSX. And then I compiled my own app with kuberl as a dependency from a Docker container running OTP 20. And then copied the .kube from my home directory to the container's home directory, so that container can see the same kube-config.

From container I can do:

root@piccolo:~# kubectl get nodes
NAME       STATUS    ROLES     AGE       VERSION
minikube   Ready     <none>    46d       v1.9.0

I got the bearer token as follows:

(piccolo@piccolo)2> Cfg.
#{api_key_prefix => #{<<"authorization">> => <<"Bearer">>},
  auth =>
      #{'BearerToken' =>
            <<"eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9"...>>},
  hackney_opts =>
      [{ssl_options,[{server_name_indication,disable}]}],
  host => "https://192.168.64.2:8443"}
(piccolo@piccolo)3> kuberl_core_api:get_api_versions(ctx:background(), #{cfg => Cfg}).
{error,#{apiVersion => <<"v1">>,code => 401,kind => <<"Status">>,
         message => <<"Unauthorized">>,metadata => #{},
         reason => <<"Unauthorized">>,status => <<"Failure">>},
       #{headers =>
             [{<<"Content-Type">>,<<"application/json">>},
              {<<"Date">>,<<"Tue, 13 Mar 2018 23:21:00 GMT">>},
              {<<"Content-Length">>,<<"129">>}],
         status => 401}}

May I know what is it I am doing wrong? Or do you think the way I am getting Bearer token is right?

How did you test this, like how to fetch bearer token, or test environment?

Thanks
-Vasu

tsloughter / kuberl Goto Github PK

kuberl's Introduction

Erlang Kubernetes client

Watch Behaviour

Using the API

Configuration

Update Generated Code

Without Nix

With Nix

kuberl's People

Contributors

Stargazers

Watchers

Forkers

kuberl's Issues

Recommend Projects

Recommend Topics

Recommend Org