Skip to content
This repository has been archived by the owner on Apr 25, 2023. It is now read-only.

Federated namespace placement doesn't recreate namespace after adding cluster back in #64

Closed
font opened this issue Apr 26, 2018 · 1 comment

Comments

@font
Copy link
Contributor

font commented Apr 26, 2018

Going through instructions at https://github.com/font/k8s-example-apps/tree/master/sample-fed-v2-demo, particularly step https://github.com/font/k8s-example-apps/tree/master/sample-fed-v2-demo#update-federatednamespaceplacement, the test-namespace is successfully removed from us-east after updating the namespace placement to remove us-east from the list of clusters.

But when the cluster us-east is added back in, the test-namespace does not get recreated in the us-east cluster causing all the other resources to no get added back due to for example:

E0426 19:44:46.756125       1 controller.go:617] Failed to execute updates for FederatedReplicaSet "test-namespace/test-replicaset": [Failed to create FederatedReplicaSet "test-namespace/test-replicaset" in cluster us-east: namespaces "test-namespace" not found]

Waiting long enough will eventually see the test-namespace created, possibly because the watch operation expires and the controller retries a list operation.

If you restart the federation pod, the test-namespace will quickly reappear in the us-east cluster after the controller receives the list of namespaces and namespace placements. The rest of the resources (configmap, secret, replicaset) then reappear as well once the test-namespace exists.

@marun
Copy link
Contributor

marun commented May 31, 2018

Fixed by #65.

@marun marun closed this as completed May 31, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants