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
Propagate annotations to the StatefulSet #932
Conversation
|
- set the type of the new configuration parameter to be array of strings - propagate the annotations to statefulset at sync
|
-handle rollingUpdate flag -modularize code -rename config parameter name
|
||
k8s.delete_operator_pod() | ||
|
||
annotations = { |
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.
is it meant to be pg_crd_annotations["metadata"]["annotations"]
?
return False | ||
for key in svc.metadata.annotations: | ||
if svc.metadata.annotations[key] != annotations[key]: | ||
return False | ||
return True | ||
|
||
def check_statefulset_annotations(self, sset_labels, annotations, namespace='default'): | ||
ssets = self.api.apps_v1.list_namespaced_stateful_set(namespace, label_selector=sset_labels, limit=1).items | ||
for sset in ssets: |
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.
Why loop if only one stateful set is fetched ?
It is effectively sset = self.api.apps_v1.list_namespaced_stateful_set(namespace, label_selector=sset_labels, limit=1).items[0]
- handle the update path to update sts and connection pooler deployment. This way no need to wait for sync - rename the parameter to downscaler_annotations - handle other review comments
👍 |
1 similar comment
👍 |
To help with this reported issue.