(k3s) Finding a starting point... #8959
Unanswered
IngwiePhoenix
asked this question in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello there!
First, for a little bit of context: I started my journey into Kubernetes late november of last year and I have now finally gotten around to deploy my first node with k3s; in total, this will span three arm64 and one riscv64 node. However, some images that I want to use don't have a riscv64 version - and some other applications I wish to deploy don't even have their own CI/CD for container images at all.
So I need to make my own! And after crawling ArtifactHub and many other k8s related resources, I ended up here.
I read through the documentation and I believe to have (finally!) found what I was looking for: A way to specify a remote, not owned by me, Git repository and then run arbitrary commands, in order, to do something with it.
But I am a little bit lost on a few details that I either didn't really get from the docs or that I might have misunderstood. Hence why I found my way here, hoping to find a few pointers. :)
There are two main pipelines that I want to run for starting out:
k3s
binary and publish it... somewhere?Both of them are straight forward; just resources pointing to Git repositories to trigger a set of jobs when ready.
Here is what I haven't managed to pick up from the docks yet:
ConfigMap
and mount that.matchLabels: { kubernetes.io/arch: arm64 }
) or on the riscv64 node respectively? As far as I understand, jobs are just a series of starting and stopping pods - so they are subjected to the regular scheduler.Thank you a lot and kind regards,
Ingwie
Beta Was this translation helpful? Give feedback.
All reactions