Skip to content
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

Specifying --blocked-nets="" does not clear the IP denylist for multihttp checks #735

Open
roobre opened this issue Jun 19, 2024 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@roobre
Copy link
Member

roobre commented Jun 19, 2024

The value of --blocked-nets, which defaults to 10.0.0.0/8, eventually makes it verbatim (after validation) to the --blacklist-ip k6 flag:

"--blacklist-ip", r.blacklistedIP,

However, specifying an empty value will not clear the in-script default value we set for multihttp checks:

Fixing this proper will require refactoring the script generation code so it can get not only check settings, but also settings local to the probe. This work was started in #732, but still requires more effort.

Workaround

A workaround for this issue is to specify a non-empty, no-op CIDR that would filter no (real) addresses, e.g. --blocked-nets=0.0.0.0/32. This will override the default value for all checks, including multihttp.

@roobre roobre changed the title Specifying --blocked-nets="" does not unblock all nets for multihttp checks Specifying --blocked-nets="" does not clear the IP denylist for multihttp checks Jun 19, 2024
@mem
Copy link
Contributor

mem commented Jun 20, 2024

Adding "component: agent" for now. That's not exactly true.

@mem mem added the bug Something isn't working label Jun 20, 2024
@peterschretlen
Copy link
Contributor

Related forum post: https://community.grafana.com/t/private-probe-and-checks-to-rfc1918/129343

I will tentatively schedule this for Cycle 25 (Nov-Dec 2024), for review during planning

@peterschretlen
Copy link
Contributor

Related to #901

@roobre
Copy link
Member Author

roobre commented Oct 28, 2024

Proposal: simply remove the hardcoded value in the script. The default value for the flag should be enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants