-
Notifications
You must be signed in to change notification settings - Fork 30
Round trip #533
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?
Round trip #533
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bn222 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 |
98d920c
to
aa8248b
Compare
Signed-off-by: Balazs Nemeth <[email protected]>
8295219
to
bdd7c9c
Compare
@wizhaoredhat ptal |
a004e1f
to
5ca6cef
Compare
/test ci/prow/make-prow-ci-manifests-check |
@bn222: The specified target(s) for
Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/test make-prow-ci-manifests-check |
Signed-off-by: Balazs Nemeth <[email protected]>
/test make-e2e-test |
/test make-e2e-test-marvell |
@bn222: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
"Intel IPU E2100": images.VspImageIntel, | ||
"Marvell OCTEON": images.VspImageMarvell, | ||
"NetSec Accelerator": images.VspImageIntelNetSec, | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will build it dynamically
@@ -6,6 +6,7 @@ metadata: | |||
subjects: | |||
- kind: ServiceAccount | |||
name: vsp-sa | |||
namespace: {{.Namespace}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
weird
name: host-root | ||
- mountPath: /var/run/ | ||
name: vendor-plugin-sock | ||
- mountPath: /opt/p4/p4-cp-nws/var |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
think about this still
type IntelDetector struct { | ||
name string | ||
} | ||
|
||
func NewIntelDetector() *IntelDetector { | ||
return &IntelDetector{name: "Intel IPU"} | ||
return &IntelDetector{name: "Intel IPU E2100"} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
const and reuse so that we don't make a mistake against the string
To avoid split-brain issues, move the creation and management of vsp pod to controller manager.