kubewire contact

[shakenfr]

hello,
sorry to distrub you in another of your project but I want to know if I can have some help with kubewire (archived project) ?

best

bruno

[djboris9]

Hi @shakenfr
Please feel free to ask the question here.

The project is archived as we don't use it anymore internally and stopped developing it. I'm not even sure, if it's able to get all resources for newer Kubernetes versions.

Boris

[shakenfr]

Hi, thanks for answer.
In fact I have 1 or 2 problems but if the first will solved maybe the second ...
When I download the release binary version, It's works under a docker with Ubuntu (20.04 for exemple) and not under Alpine (3.8 for exemple). When I put the kubewire binary inside an image like alpine3.8 , (with chmod 777 on the binary ) I obtain at launch (not such file or directory). but the kubewire bin is here with correct rights. After I try to compile as "static mode" and it's better because It accepts to launch. (maybe a pb with libc or something else) but It seems better in static mode to be compatible with many distributions).
But I doesn't resolve totally the problem. With the kubewire version (in the release) (linked dynamically) , I see all the options you mentionned on the doc. But after a compilation in static mode and even in dymanic mode (my try, maybe an error); kubewire launch is ok but without an option 👍
$ kubewire -h
...
diff Compare snapshots with another or a live cluster
help Help about any command
resourceobjects List API resource objects
serverinfo Prints server info
snapshot Take a snapshot of cluster resources and objects

It sems that
resources List API resources

is lost ! and after test there are some difference (in diff) with the result of your release and my compilation. Not expected !

So my questions : Are you sure that the release binary you provide correspond of the source that are in the master branch ?

How to compile it in static mode (with all options like missing resources option)?

Can you check that your last commit is the same that succeeds your release version ? I have a doubt of this.

best

bruno

[djboris9]

Hi Bruno

This is the latest build of it, with the code attached and commit referenced: https://github.com/postfinance/kubewire/releases/tag/v0.1.0

It's 9 commits behind master: postfinance/kubewire@v0.1.0...master

So yeah, you would need to compile this project by your own, propably with CGO_ENABLED=0

But if you want to continue this project, maybe a fork is the best option. As currently we are not developing it anymore and it's not clear if there will be a new version of it or something else.

[shakenfr]

I will fork this.

A little more question abour the usage (maybe I don't understand all in doc)

I launch
kubewire snapshot --namespaces default,kube-node-lease,kube-system,kube-public > photo1.yaml

After I delete a pod under one of these namespace

After

kubewire diff -b photo1.yaml (to compare with the live cluster)

And It returns me a lot of lines of objects like this

ResourceObjects."storage.k8s.io v1beta1 volumeattachments csi-968add91631908a5c8a11ce6745d4035deebb659d498a53d710ee6a112a0dfd5" does not exist exists
ResourceObjects."storage.k8s.io v1beta1 volumeattachments csi-9eae26758f9ad3e344bdfd09291cef6bbbf26c3ba8b5e918b969e05415634536" does not exist exists
ResourceObjects."storage.k8s.io v1beta1 volumeattachments csi-ade8d6825a76c8fb0caf0aed4d6e93b2258c1b5acee6fa96b10d3b906ed758f6" does not exist exists

but It's nor related to the pod I crash. Strange. Is it normal ?

After I take a second snapshot (photo2.yaml)
And I launch
kubewire diff -b photo2.yaml -b photo1.yaml

I have a lot of things -too many not normally impacted

and kubewire diff -b photo1.yaml -b photo2.yaml

nothing

and when I do a simple diff

diff photo1.yaml photo2.yaml
I see the pod that change.

Strange or I don't understand how to use it correctly

best

bruno