-
Notifications
You must be signed in to change notification settings - Fork 18
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
SSH: Warn when CIDR range is too large #161
Labels
component/gardenctl
Gardener CLI
kind/enhancement
Enhancement, improvement, extension
lifecycle/rotten
Nobody worked on this for 12 months (final aging stage)
Comments
sven-petersen
added a commit
to sven-petersen/gardenctl-v2
that referenced
this issue
Oct 26, 2022
including an --force flag that hides such prompts for non-interactive/script usage
sven-petersen
added a commit
to sven-petersen/gardenctl-v2
that referenced
this issue
Oct 26, 2022
including an --force flag that hides such prompts for non-interactive/script usage
sven-petersen
added a commit
to sven-petersen/gardenctl-v2
that referenced
this issue
Oct 26, 2022
including an --force flag that hides such prompts for non-interactive/script usage
sven-petersen
added a commit
to sven-petersen/gardenctl-v2
that referenced
this issue
Oct 26, 2022
including an --force flag that hides such prompts for non-interactive/script usage
sven-petersen
added a commit
to sven-petersen/gardenctl-v2
that referenced
this issue
Oct 26, 2022
including an --force flag that hides such prompts for non-interactive/script usage
sven-petersen
added a commit
to sven-petersen/gardenctl-v2
that referenced
this issue
Oct 27, 2022
including an --force flag that hides such prompts for non-interactive/script usage
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
component/gardenctl
Gardener CLI
kind/enhancement
Enhancement, improvement, extension
lifecycle/rotten
Nobody worked on this for 12 months (final aging stage)
What would you like to be added:
Similar to the confirmation screen of the access restrictions feature, the user should be warned in case the CIDR range is too large, or maybe not
/32
.Why is this needed:
It could be that auto-remediation was implemented on infrastructure accounts for non-compliant resources. One example is to prevent the usage of
/0
CIDR range.We should notify the users in case the CIDR range is too large, but leave the option to continue if the message was confirmed.
The text was updated successfully, but these errors were encountered: