python VS golang-standards/project-layout

One option is to use list_namespace(), as described in https://github.com/kubernetes-client/python/blob/master/kubernetes/docs/CoreV1Api.md

I have checked the python version == 2.7 and pip freeze - ipaddress==1.0.22, urllib3==1.24.1 and websocket-client==0.54.0 are the versions which satisfy the requirement - as mentioned here: https://github.com/kubernetes-client/python/blob/master/README.md#hostname-doesnt-matchfollowed the issue on this thread - https://github.com/kubernetes-client/python/issues/36 - not much help.

kubectl apply -f class.yamlkubectl apply -f rbac.yamlkubectl apply -f deployment-arm.yaml I want to use the kubernetes-client written in python to replace it. My current code, loads the there yaml files (using pyyaml), edits them a bit, inserts into a file and use the command line kubectl to execute those three commands. Some of the code:

In the Kubernetes Python client code it's called "klass":

https://github.com/kubernetes-client/python/blob/1a0cb469528e6b2bdeb3eb2c06945f1c22303dfd/kubernetes/client/api_client.py#L266

and in Apache ecosystem it's called clazz:

https://github.com/search?q=org%3Aapache+clazz&type=code

Just thought it was amusing and wanted to share

One way is to use configmap lock https://github.com/kubernetes-client/python/tree/master/kubernetes/base/leaderelection

I'm having trouble connecting to the kubernetes python client even though I'm following the examples here in the api.

As you can imagine, that's a lot of functions to choose from, luckily all of them are listed in docs and you can click on any one of them to get an example of its usage.

When designing a Go project, look to real-world examples like Kubernetes, Vault and the Golang Standards Project Layout. These showcase how powerful Go can be when the architecture embraces simplicity over rigid structure. Rather than trying to make Go fit a Clean Architecture mold, embrace an architecture that’s as straightforward and efficient as Go itself. This way, you’re building a codebase that’s not only idiomatic but one that’s easier to understand, maintain, and scale.

https://dev.to/booscaaa/implementando-clean-architecture-com-golang-4n0a https://github.com/golang-standards/project-layout https://blog.boot.dev/golang/golang-project-structure/ https://github.com/bnkamalesh/goapp https://www.wolfe.id.au/2020/03/10/how-do-i-structure-my-go-project/ https://blog.logrocket.com/flat-structure-vs-layered-architecture-structuring-your-go-app/ https://developer20.com/how-to-structure-go-code/ https://dev.to/jinxankit/go-project-structure-and-guidelines-4ccm https://github.com/bxcodec/go-clean-arch https://golangexample.com/example-go-clean-architecture-folder-pattern/ https://www.calhoun.io/flat-application-structure/ https://go.dev/doc/effective_go#names https://go.dev/blog/package-names

cmd: here where we will leave the main.go that starts our app.

> https://github.com/golang-standards/project-layout

The name of the repo is really and intentionally misleading. rsc filled an issue there to point this out, but the repo maintainer just disabled issues altogether so now no one can see it.

Even when it would not have such parasitic name, many seasoned Go programmers, me included, consider the self-proclaimed "Standard Go project Layout" as the opposite of what is good and advisable.

Unfortunately, the name just works, so it is being recommended all over the Internet since its inception.

Your comment makes it look as if you're saying you hate the Go development team, but it seems that isn't the case.

I get a little of what you're saying, I wouldn't say I hate anyone, but I strongly dislike how a lot of projects are organized. I think a lot stems from https://github.com/golang-standards/project-layout , which pretended to be standard and was so (ab)used one of the creators opened an issue about it. If you look at the actual Go src, it's much, much cleaner.

So you don't get blind sided for self proclaimed "standards" that are not