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

deploy: set topology feature gate to false for rbd provisioner by default #1771

Merged
merged 3 commits into from
Dec 8, 2020

Conversation

Madhu-1
Copy link
Collaborator

@Madhu-1 Madhu-1 commented Dec 8, 2020

with csi-provisioner v2.x the topology based provisioning will not have any backward compatibility with the older version of kubernetes if the nodes are not labeled with topology keys, the pvc creation is going to get fail with error accessibility requirements: no available topology found, disabling the topology based provisioning by default if the user wants to use it he can always enable it.

It also adds the default-fstype flag to the provisioner sidecar.

fixes: #1473

Signed-off-by: Madhu Rajanna [email protected]

@Madhu-1 Madhu-1 added component/deployment Helm chart, kubernetes templates and configuration Issues/PRs ready-to-merge This PR is ready to be merged and it doesn't need second review (backports only) labels Dec 8, 2020
@Madhu-1
Copy link
Collaborator Author

Madhu-1 commented Dec 8, 2020

/retest ci/centos/mini-e2e/k8s-1.18

@Madhu-1
Copy link
Collaborator Author

Madhu-1 commented Dec 8, 2020

@Madhu-1
Copy link
Collaborator Author

Madhu-1 commented Dec 8, 2020

/test ci/centos/mini-e2e/k8s-1.18

@nixpanic
Copy link
Member

nixpanic commented Dec 8, 2020

@nixpanic looks like encryption failure PTAL https://jenkins-ceph-csi.apps.ocp.ci.centos.org/blue/rest/organizations/jenkins/pipelines/mini-e2e_k8s-1.18/runs/376/nodes/89/steps/92/log/?start=0

Not sure what could cause this:

ProvisioningFailed: failed to provision volume with StorageClass "csi-rbd-sc": rpc error: code = InvalidArgument desc = invalid encryption kms configuration: missing encryption passphrase in secrets

CI jobs did pass for other runs... 🤔

with csi-provisioner v2.x the topology based
provisioning will not have any backward compatibility
with older version of kubernetes, if the nodes are
not labeled with topology keys, the pvc creation
is going to get fail with error `accessibility
requirements: no available topology found`, disabling
the topology based provisioning by default, if user want
to use it he can always enable it.

Signed-off-by: Madhu Rajanna <[email protected]>
as we are testing the topology based
provisioning in our E2E, we need to set
topology=true in E2E.

Signed-off-by: Madhu Rajanna <[email protected]>
external-provisioner is exposing a new argument
to set the default fstype while starting the provisioner
sidecar, if the fstype is not specified in the storageclass
the default fstype will be applied for the pvc created from
the storageclass.

Signed-off-by: Madhu Rajanna <[email protected]>
@nixpanic
Copy link
Member

nixpanic commented Dec 8, 2020

/retest ci/centos/mini-e2e-helm/k8s-1.19

@nixpanic
Copy link
Member

nixpanic commented Dec 8, 2020

/retest ci/centos/mini-e2e-helm/k8s-1.19

Failed deploying Rook. Not sure what the error could be.

@mergify mergify bot merged commit 518ccf4 into ceph:master Dec 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/deployment Helm chart, kubernetes templates and configuration Issues/PRs ready-to-merge This PR is ready to be merged and it doesn't need second review (backports only)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

make use of configurable fsType in the templates.
3 participants