-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve setup for a more production ready workload #2
Conversation
anubisg1
commented
Mar 31, 2022
- split gui, poller and rest into separate pods
- use env variables where needed
- poller configured as a statefulset
- use ingress to expose suzieq webui and rest server
- updated configuration files to match current suzieq requirements and showing multiple namespaces
- use official suzieq image
Hey! Thanks for the PR, more than happy to merge it, just want to take some time this weekend to try a test deployment first.. |
Thanks folks, this has been a perfect project to get me introduced to K8, really appreciate the updates to support the newest version of suzieq! |
added fsgroup to ensure it works for the non root user
I did manage to find a couple of typos, one of them in is gui.yml
|
Using manual storage currently
|
|
|
ok, that is a weird setup you have there... in my example:
i then apply all manifests:
everything works:
|
nice work! I appreciate all your efforts.....yeah, I inherited this cluster#*ck from the guy we fired ;) Trying to come up to speed but there is so much depth and I'm just getting started. |
after fixing my NFS share, it works over there too without problems
therefore i would suggest:
|
Looks like the storage is the issue now, no more pods crashing
|
did you apply the configmaps??
|
Thanks again for everything, pretty sure I can get this last issue figured out. I learned sooooo much today! |
apparently I did not....thought it would be built with the one command if I chucked it into the manifest folder but it appears it did not.....so thanks again.....I owe you a few beers ;)
|
don't worry... if you just want to test that everything works, follow the "TLDR" section in the readme. you can apply all manifests at once (and you should ;) ) .. again, check the quick instructions below
|
all issues are solved, what's left is just due bitcollector knowledge gap. |
Okay, so the issue was permissions on the worker node where these files were created! It turns out there was no write permissions by default. Man I'm ready for the weekend now! Fun times, LOL. |
update to 0.17.1
update to 0.17.1
update to 0.17.1
I ran into an issue where the poller kept crashing and also seemed to take awhile to get results so I added a second worker and bumped up the resources and things are looking much better now! Here was the error I managed to catch
|
Last step is to figure out the HA proxy for my bare metal setup, this has been kicking my butt pretty hard. It's so much easier to just use a cloud provider it seems. |
That's easy, just install metallb and configure your ingress svc with service type load balancer |
hello @hyposcaler-bot is there any expectation to merge? |
Feel free to fork, I’m overwhelmed with work, and have unfortunately been neglecting this repo.
From: Andrea Florio ***@***.***>
Sent: Monday, May 23, 2022 7:10 AM
To: hyposcaler/suzieq-on-k8s ***@***.***>
Cc: Dennis Fanshaw ***@***.***>; Mention ***@***.***>
Subject: Re: [hyposcaler/suzieq-on-k8s] improve setup for a more production ready workload (PR #2)
hello @hyposcaler-bot<https://github.com/hyposcaler-bot> is there any expectation to merge?
—
Reply to this email directly, view it on GitHub<#2 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APMPDAQHVFZ63D7T53V7MHLVLNRQNANCNFSM5SEQD5YQ>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
Adjusted the prefix in ingress