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
operator: only GC identity keys of its own cluster #16825
Conversation
3e03023
to
93a4162
Compare
93a4162
to
53d27de
Compare
53d27de
to
8cf5c69
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! A few minor comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
f7fd4e8
to
f46b0ff
Compare
test-me-please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I note that all of the Jenkins-based CI runs were successful (except test-gke), while the GHA-based CI runs were not successful. @ArthurChiao would you mind rebasing once more so we can evaluate whether the GHA-based actions were just flaky at the time or whether they were potentially revealing a real issue with the PR? |
Rebasing should fix the current AKS error. Not sure for the rest. We do still have lots of flakes in GitHub workflows. |
Fix: cilium#16805 Signed-off-by: ArthurChiao <arthurchiao@hotmail.com>
f46b0ff
to
a78502e
Compare
test-me-please Job 'Cilium-PR-K8s-GKE' failed and has not been observed before, so may be related to your PR: Click to show.Test Name
Failure Output
If it is a flake, comment Job 'Cilium-PR-K8s-1.16-net-next' failed and has not been observed before, so may be related to your PR: Click to show.Test Name
Failure Output
If it is a flake, comment |
@aanm Unfortunately this breaks multi-cluster with a fatal warning in the logs:
This happens whenever On the first order this is due to the new But more fundamentally, As this is now this PR needs to be reverted from master. |
This reverts commit e646d3e. Original PR: cilium#16825 Rationale: breaks multicluster functionality at install time with ``` level=fatal msg="Unable to initialize Identity Allocator with backend crd" error="maximum ID must be greater than minimum ID" subsys=identity-cache ``` when `--cluster-id` is set to a non-default value (e.g. `1`, as in our CI). Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
This reverts commit e646d3e. Original PR: #16825 Rationale: breaks multicluster functionality at install time with ``` level=fatal msg="Unable to initialize Identity Allocator with backend crd" error="maximum ID must be greater than minimum ID" subsys=identity-cache ``` when `--cluster-id` is set to a non-default value (e.g. `1`, as in our CI). Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
Thanks, I'll look at this tomorrow @jrajahalme |
Ref: #16805
Signed-off-by: ArthurChiao arthurchiao@hotmail.com