-
Notifications
You must be signed in to change notification settings - Fork 87
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
Switch cinder uniquePodNames to true for DCN deployments #481
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: fmount The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Do we want to set it explicitly to true, or remove it completely, thus relying on its default value and fully reverting #436 ? |
512fde1
to
c873f30
Compare
Hi @tosky, I'm ok to revert #436 entirely. I added a couple of minor changes in the way we resolve the |
This patch reverts the work done in [1], where uniquePodNames was added as a kustomization parameter for cinder and switched to false due to [2]. In addition, this patch fixes the way extraMounts Ceph secrets are accessed, and removes the not required "projected" key. [1] openstack-k8s-operators#436 [2] https://issues.redhat.com/browse/OSPRH-11240 Signed-off-by: Francesco Pantano <[email protected]>
Done |
Looks fine to me. Waiting for test results before merging. |
This patch reverts the work done in [1], where
uniquePodNames
was added as a
kustomization
parameter for Cinder and switchedto false due to [2].
In addition, this patch fixes the way
extraMounts
Ceph
secretsare accessed, and removes the not required
projected
key.[1] #436
[2] https://issues.redhat.com/browse/OSPRH-11240
Jira: https://issues.redhat.com/browse/OSPRH-11240