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

Annot via status #4

Closed
wants to merge 8 commits into from
Closed

Annot via status #4

wants to merge 8 commits into from

Conversation

kyrtapz
Copy link
Owner

@kyrtapz kyrtapz commented Aug 3, 2023

Get CI signal

@kyrtapz kyrtapz closed this Aug 3, 2023
@kyrtapz kyrtapz reopened this Aug 3, 2023
@kyrtapz kyrtapz force-pushed the annot_via_status branch 8 times, most recently from 2b1e3e1 to 115937a Compare August 7, 2023 15:56
@kyrtapz kyrtapz force-pushed the annot_via_status branch 9 times, most recently from 2b68aca to 32f1375 Compare August 17, 2023 07:19
@kyrtapz kyrtapz force-pushed the annot_via_status branch 2 times, most recently from 0807c70 to c4119e5 Compare August 22, 2023 10:59
JacobTanenbaum and others added 6 commits August 24, 2023 14:20
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]>
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.

5 participants