RHCLOUD-36142: Update Clowder to reconcile on changes to non-app secrets/configmaps
- Add hashCache to the ClowdEnvironmentReconciliation
- Remove all Secrets/ConfigMaps from Environment at start of reconciliation cycle
- Embue HashObject with the always flag
- Change updateHashCacheForConfigMapAndSecret to try to read in the sec/config and return true if always set
- Make managed_kafka add the secret to the cache at the start of reconciliation
- Update HashCache tests
- Add kuttl tests for managed kafka secrets
cc: @psav
test-config-secret-restarter is broken working on fix now.
This is looking great so far, awesome work on this @nesty156 !
e2e test fail: FAIL: kuttl/harness/test-clowdapp-watcher-kafka-msk (821.82s)
There is issue in test-clowdapp-watcher-kafka-msk-sec-source namespace pod has this Error:
test-clowdapp-watcher-kafka-msk-sec-source strimzi-topic-operator-59c597b8cb-scssl 0/1 CreateContainerConfigError 0 47s
Namespace is terminating forever:
test-clowdapp-watcher-kafka-msk-sec-source Terminating 6m5s
e2e test fail: FAIL: kuttl/harness/test-clowdapp-watcher-kafka-msk (821.82s) There is issue in test-clowdapp-watcher-kafka-msk-sec-source namespace pod has this Error: test-clowdapp-watcher-kafka-msk-sec-source strimzi-topic-operator-59c597b8cb-scssl 0/1
CreateContainerConfigError0 47s Namespace is terminating forever: test-clowdapp-watcher-kafka-msk-sec-source Terminating 6m5s
FIXED with:
- name: STRIMZI_USE_FINALIZERS value: 'false'
Seeing the unit test failure in TestMinio/createBucketsHitsCheckError, maybe due to missing config?
/retest
Did a deep dive into the code and everything looks good. I think we can move to get this rolled out. LGTM!
/retest