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

Release v0.0.8 #52

Merged
merged 5 commits into from
Feb 9, 2024
Merged

Release v0.0.8 #52

merged 5 commits into from
Feb 9, 2024

Conversation

ajfloeder
Copy link
Contributor

No description provided.

roehrich-hpe and others added 5 commits January 29, 2024 12:59
If a pod is on a host that cannot be reached, then any attempt to delete the
namespace will hang.  So change this to preserve the namespace and leave that
pod for k8s to cleanup when it can.

Signed-off-by: Dean Roehrich <[email protected]>
The Lustrefilesystem resource can get into odd situations when
namespaces are deleted. This leads to stale data in the Spec/Status
fields since nothing changes in the spec and no operator reconcile
occurs. Once this happens, PVCs will not be recreated once the namespace
comes back. This can happen when undeploying and redeploying nnf-dm when
a lustrefilesystem resource is active.

To remedy this, any change in namespaces (e.g. when nnf-dm is deployed
and the namespace is created) will trigger the reconciler and any
missing PV/PVCS will then be created.

Tested by:
1. Created a lustrefilesystem resource
2. nnf-dm then automatically adds itself to the list of namespaces in
   that resource
3. Undeploy nnf-dm (and delete namespace) - this removes the PVC
4. Redeploy nnf-dm - the PVC will be recreated mounted

Signed-off-by: Blake Devcich <[email protected]>
Signed-off-by: Anthony Floeder <[email protected]>
@ajfloeder ajfloeder changed the base branch from master to releases/v0 February 9, 2024 16:34
@ajfloeder ajfloeder merged commit 33efe58 into releases/v0 Feb 9, 2024
1 check passed
@ajfloeder ajfloeder deleted the release-v0.0.8 branch February 9, 2024 16:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants