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
Bug 2051457: CCM PodDisruptionBudgets #174
Commits on Apr 13, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 2a91c11 - Browse repository at this point
Copy the full SHA 2a91c11View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4303cd6 - Browse repository at this point
Copy the full SHA 4303cd6View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2fa51b8 - Browse repository at this point
Copy the full SHA 2fa51b8View commit details -
Add GetPlatformNameString method to operator config
For convinient obtain platfrom name as a string across operator
Configuration menu - View commit details
-
Copy full SHA for 5bee43c - Browse repository at this point
Copy the full SHA 5bee43cView commit details -
Introduce new well known labels on ccm deployments/daemonsets
infrastructure.openshift.io/cloud-controller-manager label contains platform name, intended to be used as selector for podDisruptionBudgets. For consistency reasons infrastructure.openshift.io/cloud-node-manager label was introduced for daemonsets
Configuration menu - View commit details
-
Copy full SHA for d2f73ea - Browse repository at this point
Copy the full SHA d2f73eaView commit details -
Configuration menu - View commit details
-
Copy full SHA for 053c1b1 - Browse repository at this point
Copy the full SHA 053c1b1View commit details -
Update resourceapply test for using envtest and gomega matcher
Expected to fail, respective resourceapply changes for handling Deployment coming next commit
Configuration menu - View commit details
-
Copy full SHA for e1f47b7 - Browse repository at this point
Copy the full SHA e1f47b7View commit details -
Add recreate procedure for deployment and daemonsets in case of chang…
…ed selectors Selectors are immutable for Deployments and DaemonSets, in case if it was changed, delete old and create new one with prior serverside validation
Configuration menu - View commit details
-
Copy full SHA for 1bf44f1 - Browse repository at this point
Copy the full SHA 1bf44f1View commit details -
Configuration menu - View commit details
-
Copy full SHA for d3be146 - Browse repository at this point
Copy the full SHA d3be146View commit details -
Configuration menu - View commit details
-
Copy full SHA for d4b6c3f - Browse repository at this point
Copy the full SHA d4b6c3fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 5b17fa2 - Browse repository at this point
Copy the full SHA 5b17fa2View commit details -
remove recursion, some err handling inlining
DRY principle does not work well in this world, sorry
Configuration menu - View commit details
-
Copy full SHA for a496360 - Browse repository at this point
Copy the full SHA a496360View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7993147 - Browse repository at this point
Copy the full SHA 7993147View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9429f58 - Browse repository at this point
Copy the full SHA 9429f58View commit details -
Configuration menu - View commit details
-
Copy full SHA for 599c739 - Browse repository at this point
Copy the full SHA 599c739View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7488432 - Browse repository at this point
Copy the full SHA 7488432View commit details