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

Fix Deseeding of Service User #58

Closed
BugRoger opened this issue Sep 26, 2017 · 5 comments
Closed

Fix Deseeding of Service User #58

BugRoger opened this issue Sep 26, 2017 · 5 comments
Labels

Comments

@BugRoger
Copy link
Contributor

When a cluster is deleted the service user needs to be cleaned up

@databus23
Copy link
Member

I think this is already implemented. See

glog.Infof("Deleting openstack user %s@%s", tpr.Spec.OpenstackInfo.Username, tpr.Spec.OpenstackInfo.Domain)
if err := op.Clients.Openstack.DeleteUser(tpr.Spec.OpenstackInfo.Username, tpr.Spec.OpenstackInfo.Domain); err != nil {
return err
}

@BugRoger
Copy link
Contributor Author

Ok, cool. Though:

image

@BugRoger BugRoger changed the title Deseeding of Service User Fix Deseeding of Service User Sep 26, 2017
@databus23
Copy link
Member

For the deseeding to work the cluster TPR must not be deleted using kubectl. I can only imagine this has happened here. Lets leave this open for now and see if this keeps happening again.

@BugRoger
Copy link
Contributor Author

Those klusters have all been deleted via Elektra.

@databus23
Copy link
Member

I've cleaned up all service users in staging that were not correctly removed when the cluster was deleted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants