Replies: 3 comments 10 replies
-
|
Beta Was this translation helpful? Give feedback.
-
|
Maybe another general question on the topic how to test: Is a compiled binary like go the way to go or would something in the realm of bash be a better fit.
The drawback would be: bash .. it can get messy real quick |
Beta Was this translation helpful? Give feedback.
-
|
go compilation is quick enough that it doesn't make a noticeable difference in practice and pretty much all components we'd like to test are written in go as well. Python might be viable alternative, but meaningful tests in bash won't be much fun. |
Beta Was this translation helpful? Give feedback.
-
|
The compilation time wasn't my concern, more over the toolchain needed to compile go. Maybe a docker-dev setup that would allow a "zero-requirement" usage could be helpful. (I have basically zero knowledge of go 🙈) |
Beta Was this translation helpful? Give feedback.
-
|
The "toolchain" you'd need for go is a single binary, anything else (like the tests build-time dependencies) is automatically fetched during runtime. Docker alone is more complex than that |
Beta Was this translation helpful? Give feedback.
-
|
I think its time for me to check it finally out! |
Beta Was this translation helpful? Give feedback.
-
|
@captnCC Thanks for re-viving the matter. Your proposal of testing in one's own account is a great idea! I had kept the About the choice of language, whatever you see fit yourself. I myself am more of a Python dev, but Go is probably worth learning when you work with Kubernetes. |
Beta Was this translation helpful? Give feedback.
-
|
@captnCC This would really help all of us -- You do not know how much of my time goes into testing all possible use cases for each major PR, it's just a pain in the bum! 🤦 So really glad you are reviving this... 🙏 (please do not miss the add-testsuite banch, if you wish to build upon phaer's work, or at least inspire yourself from it). Both Python and Go seems decent for me. Bash on the other hand, I think it's too low level. |
Beta Was this translation helpful? Give feedback.
-
|
Just another note for people working on testing kube-hetzner: https://github.com/syself/cluster-api-provider-hetzner mentions that hetzner sponsors e2e test infrastructure for them. Might be worth asking them ;) (won't do it myself as I am not using kube-hetzner myself anymore) |
Beta Was this translation helpful? Give feedback.
-
|
Good to know! I will ask, as soon as we have something working! |
Beta Was this translation helpful? Give feedback.
-
@phaer Why is this? What you are using now? |
Beta Was this translation helpful? Give feedback.
-
|
@ifeulner I have no need for kubernetes anymore, just using normal nixos boxes. |
Beta Was this translation helpful? Give feedback.
-
|
@phaer But it's still nice that we still get to pick your brain on important issues! Thanks for that... 🙏💙 |
Beta Was this translation helpful? Give feedback.
-
In an attempt do ease the process to test and verify on merge requests it might be good idea to start with a list of test setups that could be run at least locally against own hetzner accounts. I remember there was an PR to provide testing with go, but I can't find it anymore.
So I will just start with the cases I can imagine and which have causes problems in the past:
The list could continue with a variation of addons, but I don't have any expertise in that. Especially the storage options with longhorn and/or hetzner volumes would make a good addition to create more trust in their functionality!
Beta Was this translation helpful? Give feedback.
All reactions