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

Document network flows #1467

Open
jemag opened this issue Sep 12, 2024 · 2 comments
Open

Document network flows #1467

jemag opened this issue Sep 12, 2024 · 2 comments

Comments

@jemag
Copy link

jemag commented Sep 12, 2024

Use-Case

Current documentation does not clearly outline the necessary network flows needed for KEDA to work. This makes it significantly harder to write appropriate restrictive network policies for KEDA.

Although there is

They are not sufficient nor precise enough.

I would expect rather something like:

Specification

  • Describe each flow required to allow KEDA to work in the context of network policies.

Example:
keda-operator:
oubound

  • Allow communication to API server on port 443
    Etc.

inbound

  • Allow communication from monitoring agent on port 8080
  • Allow communication from keda-operator-metrics on port 9666
    Etc.
Copy link

stale bot commented Nov 13, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Nov 13, 2024
@jemag
Copy link
Author

jemag commented Nov 14, 2024

/not-stale

@stale stale bot removed the stale All issues that are marked as stale due to inactivity label Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant