test #384
Closed
test #384
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…hift#259) Upstream-commit: c6d2f45bf2e87da37ba1abd19a969faa7975e582 Upstream-repository: api
…extConfig (openshift#261) Accepted values for SecurityContextConfig(string): legacy/resctricted(default) Upstream-commit: dfe859e2cf10757aa4cd0eef99917637c8feace9 Upstream-repository: api
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: timflannagan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
The hack script needs to be fixed but I did see a diff present when running the following: $ rm -rf staging/*/vendor
$ git status
deleted: staging/operator-lifecycle-manager/vendor/github.com/operator-framework/api/crds/operators.coreos.com_catalogsources.yaml
deleted: staging/operator-lifecycle-manager/vendor/github.com/operator-framework/api/crds/zz_defs.go
deleted: staging/operator-lifecycle-manager/vendor/github.com/operator-framework/api/pkg/manifests/bundleloader.go
deleted: staging/operator-lifecycle-manager/vendor/github.com/operator-framework/api/pkg/operators/v1alpha1/catalogsource_types.go
deleted: staging/operator-lifecycle-manager/vendor/modules.txtLooks like the commits might've introduced some nested vendor changes. Not too sure whether that's the culprit here. |
…(#2845) * (chore) vendor in o-f/api v0.17.1 Signed-off-by: Anik Bhattacharjee <[email protected]> * (psa) allow legacy Catalogsources to run in non-restrcted namespaces This PR configures the Catalogsource reconciler to use the spec.GrpcPodConfig.SecurityContextConfig field to determine if the pod.spec.securityContext and container[*].spec.SecurityContext for the registry pod should be configured to be runnable in a PSA restrcited namespace or not, so that cluster admins can indicate that they want to run legacy catalogsources in a non-resctricted (baseline/privileged) namespace. This allows cluster admins to run catalogsources that are built with a version of opm that is less than v1.23.2 (i.e a version of opm that does not contain [this commit](operator-framework/operator-registry#974) Signed-off-by: Anik Bhattacharjee <[email protected]> Signed-off-by: Anik Bhattacharjee <[email protected]> Upstream-commit: edffd9c83c3065073e5f91ff0d7c7b78a5c77063 Upstream-repository: operator-lifecycle-manager
timflannagan
force-pushed
the
unit-psa-test
branch
from
4e5d752 to
6bdc9f8
Compare
|
Closing as the OLM unit check is now back online. |
perdasilva
pushed a commit
to perdasilva/operator-framework-olm
that referenced
this pull request
Jan 15, 2025
Bumps [k8s.io/client-go](https://github.com/kubernetes/client-go) from 0.31.3 to 0.32.0. - [Changelog](https://github.com/kubernetes/client-go/blob/master/CHANGELOG.md) - [Commits](kubernetes/client-go@v0.31.3...v0.32.0) --- updated-dependencies: - dependency-name: k8s.io/client-go dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Signed-off-by: Per Goncalves da Silva <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Upstream-repository: api Upstream-commit: 8fae9f55f61c1e7236e98570b86767c1b97c49f2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
wip