-
Notifications
You must be signed in to change notification settings - Fork 293
feat(KFLUXVNGD-332): deploy smee-sidecar in production #6942
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
feat(KFLUXVNGD-332): deploy smee-sidecar in production #6942
Conversation
65ae87e
to
7406b42
Compare
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.
/lgtm
7406b42
to
e955b1d
Compare
/lgtm |
This change moves the manifests for deploying smee with the sidecar from the staging overlays (client and server) to the base, and having both staging and prod reference them. Signed-off-by: Yftach Herzog <[email protected]>
e955b1d
to
3313887
Compare
/retest-required |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: avi-biton, ifireball, yftacherzog 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 |
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. |
Going to do this in smaller steps on multiple PRs |
This change moves the manifests for deploying smee with the sidecar from the staging overlays (client and server) to the base, and having both staging and prod reference them.