-
Notifications
You must be signed in to change notification settings - Fork 374
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
Provide better defaults for external-snapshotter #459
Conversation
Welcome @kvaps! |
Hi @kvaps. Thanks for your PR. I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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/test-infra repository. |
ed88539
to
2db4645
Compare
/assign @jingxu97 |
/ok-to-test |
/retest |
e33a43f
to
cc157ce
Compare
cc157ce
to
2db4645
Compare
c14e1af
to
7ac6f0c
Compare
/retest |
@@ -9,13 +9,12 @@ apiVersion: v1 | |||
kind: ServiceAccount | |||
metadata: | |||
name: snapshot-controller | |||
namespace: default # TODO: replace with the namespace you want for your controller, e.g. kube-system | |||
namespace: kube-system |
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.
This is used in CI so I'd like to ask Patrick to take a look.
@pohly Do you have any concerns for this namespace to be changed from "default" to "kube-system"?
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.
No objections.
Just beware that it might be necessary to change prow.sh so that it works with a rbac-snapshot-controller.yaml that has namespace: default
(current stable release) and a newer rbac-snapshot-controller.yaml that has namespace: kube-system
(canary) because the same prow.sh file is used with both, depending on the test job.
release-tools/prow.sh
Outdated
if [ $cnt -gt 30 ]; then | ||
echo "snapshot-controller pod status:" | ||
kubectl describe pods -l app=snapshot-controller | ||
kubectl describe pods -n "$expected_namespace" -l app=snapshot-controller |
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.
prow.sh should be changed in csi-release-tools first.
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.
Sure, It has been changed already, PR kubernetes-csi/csi-release-tools#121
f6a1b62
to
778e3c0
Compare
The release-tools change is already included in this PR: #464. Can you remove those changes from your PR and rebase? |
Sure, rebased |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kvaps, xing-yang 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 |
Hi. Is it possible to create release with this change? |
This affects multiple sidecars because we have to make changes in release-tools. I don't think this is a bug fix that can be backported. The yaml files are provided as examples. User can modify their own yamls if needed. Our usual release timeline aligns with the next k8s release. |
Got it! Thank you |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Provided manifests for external-snapshotter are not optimal in most use-cases.
Since external-snapshotter is most common component among various Kubernetes distributions and csi-plugins, I think we need to correct the manifests and include the following changes. They are needed to simplify the setup and provide optimal defaults for every user.
The following changes would allow to simple install working external-snapshotter using just few commands, as described here:
https://kubernetes-csi.github.io/docs/snapshot-controller.html#deployment
but without having to manually edit manifests
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: