backup-restore-operator
backup-restore-operator copied to clipboard
rancher
V2 Add ingress to networkpolicy allow all
@eliyamlevy @superseb the unit tests seem to be "broken" rather than an issue with the change itself
Error: unknown flag: --helm3
Usage:
unittest [flags] CHART [...]
This requires https://github.com/rancher/backup-restore-operator/pull/320 to be backported
@r2ronoha From what I know we're not cutting a new version of the release/v2.0 line this quarter. I can look into bringing this in for the next. Also if you would please write some context as to why you want this change (your pr) merged that would be great.
if you would please write some context as to why you want this change (your pr) merged that would be great.
The policy missing the ingress attribute blocks all ingress traffic, as opposed to allow (as the policy is intended to do). We are currently using a Kustomize override to add it, as it breaks access from the rest of the cluster to the resources in the namespace.
This repository uses an automated workflow to automatically label pull requests which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community pull requests better. If the pull request is still relevant, please add a comment to the pull request so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the pull request in 14 days. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
@r2ronoha From what I know we're not cutting a new version of the release/v2.0 line this quarter. I can look into bringing this in for the next. Also if you would please write some context as to why you want this change (your pr) merged that would be great.
This is still active. Waiting for release/v2.0 as per comment above
Hello, please work on getting the build to pass if you choose to develop it yourself.
EDIT: Just saw the aboe comment, got swamped with other things I'll bring this up and see
This repository uses an automated workflow to automatically label pull requests which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community pull requests better. If the pull request is still relevant, please add a comment to the pull request so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the pull request in 14 days. Thank you for your contributions.
This repository uses an automated workflow to automatically label pull requests which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community pull requests better. If the pull request is still relevant, please add a comment to the pull request so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the pull request in 14 days. Thank you for your contributions.
This repository uses an automated workflow to automatically label pull requests which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community pull requests better. If the pull request is still relevant, please add a comment to the pull request so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the pull request in 14 days. Thank you for your contributions.
Could you rebase this PR off the release/v4.0 branch?
And also please explain why this PR is needed, as there's no associated issue.
What difference would I observe with this change in place, and how would I trigger it?
This repository uses an automated workflow to automatically label pull requests which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community pull requests better. If the pull request is still relevant, please add a comment to the pull request so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the pull request in 14 days. Thank you for your contributions.