forked from ovn-org/ovn-kubernetes
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Annot via status #4
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kyrtapz
force-pushed
the
annot_via_status
branch
8 times, most recently
from
August 7, 2023 15:56
2b1e3e1
to
115937a
Compare
kyrtapz
force-pushed
the
annot_via_status
branch
9 times, most recently
from
August 17, 2023 07:19
2b68aca
to
32f1375
Compare
kyrtapz
force-pushed
the
annot_via_status
branch
2 times, most recently
from
August 22, 2023 10:59
0807c70
to
c4119e5
Compare
Signed-off-by: Jaime Caamaño Ruiz <[email protected]>
Signed-off-by: Jaime Caamaño Ruiz <[email protected]>
kyrtapz
force-pushed
the
annot_via_status
branch
from
August 24, 2023 16:29
c4119e5
to
7f3be80
Compare
clearInitialNodeNetworkUnavailableCondition needs to be run on every node for GCP. Since we have some nodes that are not running ovn-kubernetes, notably windows, it should be run in the clustermanager Signed-off-by: Jacob Tanenbaum <[email protected]>
Fix encap port configuration for remote chassis
…ndition move clearInitialNodeNetworkUnavailableCondition to clustermanager
This commit updates ovnkube-trace readme file according to latest changes for adapting interconnect feature and support for tracing dual stack cluster. Signed-off-by: Periyasamy Palanisamy <[email protected]>
Changes to metadata via status subresources are not restricted for the basic kubernetes types. This means we can set the status/annotations/labels with only the status subresource permissions. Upstream note: kubernetes/kubernetes#92022 (comment) Signed-off-by: Patryk Diak <[email protected]>
This commit refactors the RBAC rules and serviceAccount ovn-kubernetes uses in KIND deployments. Instead of using one ServiceAccount with one ClusterRole break it down per component. This makes it easier to track which permissions are required by which piece and avoid the mess of granting high privilages to everyone. Signed-off-by: Patryk Diak <[email protected]>
kyrtapz
force-pushed
the
annot_via_status
branch
from
August 28, 2023 11:29
7f3be80
to
a9d1995
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Get CI signal