[
https://issues.jboss.org/browse/WFWIP-187?page=com.atlassian.jira.plugin....
]
Jeff Mesnil commented on WFWIP-187:
-----------------------------------
I'm not sure there is an issue here and it seems to work as expected for PVC.
https://kubernetes.io/docs/tasks/run-application/delete-stateful-set/#per...:
Deleting the Pods in a StatefulSet will not delete the associated volumes. This is to
ensure that you have the chance to copy data off the volume before deleting it. Deleting
the PVC after the pods have left the terminating state might trigger deletion of the
backing Persistent Volumes depending on the storage class and reclaim policy. You should
never assume ability to access a volume after claim deletion.
Changes to PVC are not reflected in Operator
--------------------------------------------
Key: WFWIP-187
URL:
https://issues.jboss.org/browse/WFWIP-187
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Martin Choma
Assignee: Jeff Mesnil
Priority: Blocker
Labels: operator
Any chnages (adding, removing or updating) made to PVC after WildFlyServer CR was created
are not reflected in underlying PVC kubernetes object.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)