-
Notifications
You must be signed in to change notification settings - Fork 103
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
Fix ArgoCD diff on postgresql keys #441
Conversation
9048090
to
6fb2639
Compare
If there are other problems like this, give me the key names, and I will fix them. |
@bozorgmehr96 this is my ignoreDifferences rule: group: postgresql.cnpg.io
kind: Cluster
jsonPointers:
- /spec/bootstrap/initdb/postInitApplicationSQL
- /spec/managed
- /spec/postgresql/shared_preload_libraries
- /spec/priorityClassName
- /spec/postgresql/pg_hba
- /spec/postgresql/pg_ident You covered the last two for me |
@pschichtel Thanks. I wrapped them in if blocks. |
13ae008
to
f8e49c2
Compare
Signed-off-by: Mohammad Bozorgmehr <[email protected]>
Signed-off-by: Mohammad Bozorgmehr <[email protected]>
Signed-off-by: Mohammad Bozorgmehr <[email protected]>
Signed-off-by: Mohammad Bozorgmehr <[email protected]>
Signed-off-by: Mohammad Bozorgmehr <[email protected]>
Signed-off-by: Mohammad Bozorgmehr <[email protected]>
f8e49c2
to
d08bd5a
Compare
@bozorgmehr96 one more:
|
@pschichtel, can you provide a repro? It has a non-empty default value, so it shouldn't have the problem I'm trying to fix here. |
@bozorgmehr96 I customized the schedule, so I don't get the defaults since it's an array. According to charts/charts/cloudnative-pg/templates/crds/crds.yaml Line 15655 in fb45e4f
charts/charts/cloudnative-pg/templates/crds/crds.yaml Line 15575 in fb45e4f
|
I am getting a few items in argocd that are oddly just missing on the live manifest. Not sure if it's the CRD/operator or something with values that might be false by default removed or if these values don't exist anymore?
There might be more since we didn't set them all. Here are other issues just to list them all. Some are shown in other places. I think the issue is clearly the operator doesn't generate these empty or default values in the spec it creates. |
Signed-off-by: Mohammad Bozorgmehr <[email protected]> Signed-off-by: Itay Grudev <[email protected]> Co-authored-by: Mohammad Bozorgmehr <[email protected]> Co-authored-by: Itay Grudev <[email protected]>
Use
with
for every key in the cluster'sspec.postgresql
to prevent generating empty keys.Fixes: #426