-
Notifications
You must be signed in to change notification settings - Fork 58
Karmada client integration k8s #215
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
base: main
Are you sure you want to change the base?
Karmada client integration k8s #215
Conversation
'(?:169\\.254|192\\.168)(?:\\.\\d{1,3}){2})(?!172\\.(?:1[6-9]|2\\d|3[0-1])(?:\\.\\d{1' + | ||
',3}){2})(?:[1-9]\\d?|1\\d\\d|2[01]\\d|22[0-3])(?:\\.(?:1?\\d{1,2}|2[0-4]\\d|25[0-5])' + | ||
'){2}(?:\\.(?:[1-9]\\d?|1\\d\\d|2[0-4]\\d|25[0-4]))|(?:(?:[a-z\\u00a1-\\uffff0-9]-*)*' + | ||
'[a-z\\u00a1-\\uffff0-9]+)(?:\\.(?:[a-z\\u00a1-\\uffff0-9]-*)*[a-z\\u00a1-\\uffff0-9]' + |
Check failure
Code scanning / CodeQL
Inefficient regular expression High
/assign @warjiang |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@MdSayemkhan could you follow the instruction of DCO bot and fix the problem of dco? |
Signed-off-by: MdSayemkhan <[email protected]>
…importing packages Signed-off-by: MdSayemkhan <[email protected]>
Signed-off-by: MdSayemkhan <[email protected]>
Signed-off-by: MdSayemkhan <[email protected]>
70c7477
to
2cdefdc
Compare
… to patch Signed-off-by: MdSayemkhan <[email protected]>
Signed-off-by: MdSayemkhan <[email protected]>
The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the karmada-io org. You can then trigger verification by writing
|
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #214
Special notes for your reviewer:
Does this PR introduce a user-facing change?: