kubernetes-client VS yq

While that is true I‘d like to suggest taking a look at this client: https://github.com/fabric8io/kubernetes-client

I am trying to program the patching/rolling upgrade of k8s apps by taking deployment snippets as input. I use patch() method to apply the snippet onto an existing deployment as part of rollingupdate using fabric8io's k8s client APIS.. Fabric8.io kubernetes-client version 4.10.1I'm also using some loadYaml helper methods from kubernetes-api 3.0.12.

This approach works fine on our DIND-Kubernetes environment. However, when tried to port the deployment onto a Docker-EE Kubernetes environment we ran into trouble because the command kubectl label pod generates a run time error which is completely misleading (also see https://github.com/fabric8io/kubernetes-client/issues/853).

To be specific, I am trying to use https://github.com/fabric8io/kubernetes-client/tree/master/crd-generator in scala code. If it is only duplicating one class or so, that seems manageable. But if I need to rewrite everything I am less confident

In terms of spinning up and managing everything, like, the stuff that's not Java apps. But some of the old fabric8 work - the predecessor to jKube - provides Java APIs and utilities to doing things like writing kubernetes operators in Java. Check out the kubernetes-client project. A lot of people never even learn about kubernetes operators, and just think "I have a service, la la la" plug their ears and then assume there will be some magic operational team that will deploy some service mesh app to solve all their problems.

Fabric8 is a very good Solution. I played also with k8s provided solution but especially custom resource definitions are a hell. I can recommend fabric8 it’s also used in operators like strimzi https://github.com/fabric8io/kubernetes-client

As the name says, this article is all about how to Cancel TaskRuns in Tekton using the Fabric8 Tekton client. You can see the latest example code here

Can the service account token, be used programmtically e.g., using https://github.com/fabric8io/kubernetes-client ?

What I often use to just get the full key paths is yq (https://github.com/mikefarah/yq), piping into grep when necessary

  yq -o=props 

For more information about this command visit https://github.com/mikefarah/yq

I've been trying to install and config a plugin (papis.nvim) for a couple of days and am having issues with a function that uses io.popen to run yq to convert yaml files to json. I know my install of yq is fine- I can run yq -oj info.yaml from the command line with no issue and it produces the correct json output. I know the function can find the yq executable, but it returns nil. I've saved the error from the yq golang code: panic: runtime error: invalid memory address or nil pointer dereference

- yq has no if-then-else https://github.com/mikefarah/yq/issues/95 which is a poor design (or omission) in my opinion

After which, I use openapi-generator to make a yaml output.

https://gist.github.com/freshteapot/3637e8d2b5ecdf01b7d25246...

- yq version 3.4.1 (Worth noting, the example uses an out of date yq, so a few modifictaions might be needed)

https://github.com/mikefarah/yq

For those pining for a similar yaml query tool for working through acres of config: https://github.com/mikefarah/yq

jq is awesome and thanks to the new team for their recent efforts and energy, it massively appreciated.

For anyone looking for such a script, there's some CLIs that make it easy. One is `yq -o props` [1], another way is to use `yq -j` or `yj` [2] to convert to JSON and pipe it to `gron` [3].

[1] https://github.com/mikefarah/yq

[2] https://github.com/sclevine/yj

[3] https://github.com/tomnomnom/gron