Skip to content
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

Update ENV variable name in syncer to match with the deployment yaml file #65

Merged
merged 1 commit into from
Sep 26, 2019
Merged

Update ENV variable name in syncer to match with the deployment yaml file #65

merged 1 commit into from
Sep 26, 2019

Conversation

chethanv28
Copy link
Collaborator

@chethanv28 chethanv28 commented Sep 24, 2019

What this PR does / why we need it:
This PR will fix the ENV variable name for FULL SYNC interval in syncer source files to match with the ENV specified in the deployment file
We need this change for users to customize the full sync interval and for this the ENV variables in the source code must match with the deployment yaml file
https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/manifests/1.14/deploy/vsphere-csi-controller-ss.yaml

Special notes for your reviewer:
Deploy CSI driver and customize the value of the FULL SYNC to different values.
Currently the default value is set to 30minutes both in the source files and yaml file. But with this change, if users change the FULL SYNC to different value it will be reflected in the container at runtime as well

Release note:

Fix ENV variable to support customization of FULL SYNC interval

Snapshot of the Deployment file:

kind: StatefulSet
apiVersion: apps/v1
metadata:
  name: vsphere-csi-controller
  namespace: kube-system
...
...
...
        - name: vsphere-syncer
          image: <repository:image-name:tag>
          args:
            - "--v=2"
          imagePullPolicy: "Always"
          env:
            - name: FULL_SYNC_INTERVAL_MINUTES
              value: "30"
            - name: VSPHERE_CSI_CONFIG
              value: "/etc/cloud/csi-vsphere.conf"
          volumeMounts:
            - mountPath: /etc/cloud
              name: vsphere-config-volume
              readOnly: true

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Sep 24, 2019
@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Sep 24, 2019
@k8s-ci-robot
Copy link
Contributor

Hi @chethanv28. Thanks for your PR.

I'm waiting for a kubernetes-sigs or kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Sep 24, 2019
@RaunakShah
Copy link
Contributor

I'd suggest changing the environment variable in the YAML to FULL_SYNC_INTERVAL_MINUTES. Full Sync is a CNS concept and doesn't need the CSI prefix.

@chethanv28
Copy link
Collaborator Author

I'd suggest changing the environment variable in the YAML to FULL_SYNC_INTERVAL_MINUTES. Full Sync is a CNS concept and doesn't need the CSI prefix.

@RaunakShah I have addressed your review comment in the latest commit

@davidvonthenen
Copy link
Contributor

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Sep 25, 2019
@divyenpatel
Copy link
Member

@chethanv28 please squash all your commits. LGTM

@chethanv28
Copy link
Collaborator Author

@chethanv28 please squash all your commits. LGTM

@divyenpatel I have squashed all the commits

@divyenpatel
Copy link
Member

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 25, 2019
@divyenpatel
Copy link
Member

/approve

@chethanv28
Copy link
Collaborator Author

/assign @dvonthenen
/assign @codenrhoden

@davidvonthenen
Copy link
Contributor

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chethanv28, divyenpatel, dvonthenen

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 26, 2019
@k8s-ci-robot k8s-ci-robot merged commit 27927bf into kubernetes-sigs:master Sep 26, 2019
@chethanv28
Copy link
Collaborator Author

Thanks for the approvals @dvonthenen and @divyenpatel

gnufied pushed a commit to gnufied/vsphere-csi-driver that referenced this pull request May 3, 2023
…3-27561-downstream

OCPBUGS-8457: UPSTREAM: 2326: Update opencontainers/runc for CVE-2023-27561
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants