Meowbernetes Mini

Devlog 7: its getting hard now
working on scheduler. added a skeleton for get current and desired state, refactored the parsing config. and more. many issues mainly around desired state and designing it, and a few other minor hiccups. errors are from protos not being updated in go yet not a real issue(i think)

Devlog 6: edited tui, and finished server side stuff till i update protobuffer.

No issues this time! i’ve added ttl to redis, ill add more functions, im gonna work on client side stuff then sechdular, after that its time for the binary and probably more interfaces to make sure everything works because i got lazy and didn’t do that for Redis bad SOC but idc!

Devlog 5: gRpc is actually easy
yeah i dunno why i got confused besides refusing to read docs pretty intuitive to use with go Progress: got most of the two internal daemons done server side, scheduler and client side still need to be done, added a way to keep up with heartbeats so it can actually be used. and decided on naming(on parts) and removed redundancy. Some issues i’ve ran into were i was going to recreate etcd but to complex to re do design i had in mind to fit around that and im just to lazy to anyways, and figuring out how redis with go works but didn’t take long. but mainly a me wasting time just to end up removing them for a more efficient way to, and making sure everything matches, and not an issue(as of now) but ill have to deal with it in future, req.id PROBABLY isn’t gonna match container id and stuff and no clue if i still need to pull image, ill work on that but an issue that’s going to get me later. smaller devlog still takes me too long though!

Devlog 4: GRPC IS CONFUSINGGGG
this took way to longer, i thought i knew grpc better because i watched a YouTube video on it weeks ago but i finally understand it now, I added Ymal parsing/config, i refactored file structure some, i plan to replace registry with Redis, and ill add a JSON backup so if daemon/tui/ whatever is restarted or for whatever reason fails ill be able to back up stuff or user will be able to. main hiccups were file structure and figuring out grpc, ymal took some time to figure out docs but relatively self explanatory, but i also haven’t tested it so maybe not . i don’t plan on making a actual etc so like mentioned im going to use Redis in its place.

Devlog 3: Took a bit too long! ive mainly been reading moby/container docs, and kuberenetes docs. because i dont actually use it so i wanted to make sure understating is correct and everything(mostly because im too lazy to do it all) matches. added docker functionality, well not really i added a interface and test ill do real docker once ymal and everything else is set up, i did MAINLY set up ymal parsing but not fully complete. pretty productive, i thought i was relearning go but i guess i didn’t know much about it outside of api so its a good learning experience. no issues on this log, besides it taking a while due to refactoring and wanting everything to fit together nicely + SOC. ill likely start developing faster once im free from this config stuff.

Devlog 2: protobuffer was easier than i thought to set up, i refactored a couple files to match/ separate concerns, no hiccups i just had to switch from pycharm to goland(because im a jetbrains fanboy and wont use vs code or vim) that’s all for now. next ill work on finishing go and node and possibly mounting on to docker or figuring out how kuberentes does that.

Devlog 1: Set up the basics and made a rip off logo
nothing eventful, i set up bubble tui, nodes(cats) and pods(paws) types and go, making the protobuffer for hearbeats and stuff next