reflector | Burp plugin able to find reflected XSS | Reflection library

I am running archlinux(arcolinux distro to be specific) everything is fine but one little tiny problem which annoys me the problem is every time i open a terminal this pops us at the top of the terminal

"Linux pengu 5.15.25-1-lts x86_64 unknown"

I know this is a uname command with custom flags however I don't have that in my config.fish(I use fish shell(I run fish with bash i), I am aware that every time I open a my fish shell the stuff in my config.fish run, is there anything I am missing or what? here is my config.fish:

{

I want to get an ObjectId from my mongo database, but with async / await, i get an error:

ERROR [ExceptionsHandler] Query was already executed: Role.findOne({ name: { '$in': [ 'admin' ] } }) MongooseError: Query was already executed: Role.findOne({ name: { '$in': [ 'admin' ] } })

I want to call mongoose asynchronously because my userRoles array is empty when i want to use it after this code block;

here's the code role.guard.ts

When I run any PHP artisant command I got this Error

when i include @Permissions('read') my acessGuard stops receiving JWT info, @Permissions simply sets metadata (code below)

I'm working on aws eks, and I'm having issues with networking because none of the pods can resolve hostnames.

Checking the kube-config pods, I found this:

I have created a guard in a separate module for checking feature flags as below

We performed our kubernetes cluster upgrade from v1.21 to v1.22. After this operation we discovered that our nginx-ingress-controller deployment’s pods are failing to start with the following error message: pkg/mod/k8s.io/client-go@v0.18.5/tools/cache/reflector.go:125: Failed to list *v1beta1.Ingress: the server could not find the requested resource

We have found out that this issue is tracked over here: https://github.com/bitnami/charts/issues/7264

Because azure doesn't let to downgrade the cluster back to the 1.21 could you please help us fixing the nginx-ingress-controller deployment? Could you please be specific with what should be done and from where (local machine or azure cli, etc) as we are not very familiar with helm.

This is our deployment current yaml:

I am trying to follow the official documentation on how to install a single node OKD 4.9 cluster from these links:

• https://docs.okd.io/4.9/installing/installing_sno/install-sno-preparing-to-install-sno.html
• https://docs.okd.io/4.9/installing/installing_sno/install-sno-installing-sno.html

Here is my network topology:

Here is the pfsense DHCP configuration that makes all the hosts have static IP addresses:

Here is the pfsence DNS configuration:

Here is my install-config.yaml:

I am using keepalived from default yum v1.3.5 (03/19,2017), git commit v1.3.5-6-g6fa32f2 on centos 7 (2009)

The vip is working properly but when I add notify script, it was opening the file but not running it (I guess). This is my config file of my backup. I used root because I read somewhere that keepalived need privilege similar to root (I can be wrong on this)