Copy existing rules when updating instance ingress eclipsesource/theia-cloud#206
use lookup function to find existing rules
Remove lookups from base eclipsesource/theia-cloud#204
we allow to customize the name. user shall customize the name if they get any conflicts on install. using lookup like this leads to removal of the resources if they are existing
Add configmap checksums to deployments eclipsesource/theia-cloud#202
will restart the deployments when there configmap changes
Ingress update should be tested with 2-01_try-now (subdomain based) and 2-03_try-now_paths (path based) test-configurations.
Install test configuration
Change something in instances-ingress-path-based.yaml and instances-ingress.yaml e.g. increase the nginx.ingress.kubernetes.io/proxy-buffer-size slightly and update the helm chart version
run terraform apply again with new chart. Verify that the changed value in the ingress has changed
Start a session, repeat above steps, and verify the the session is still reachable with the same URL
Start a further sessions, repeat above steps, and verify that both the sessions are still reachable with their URLs.
Test again with other test-configuration
Base chart upgrade can be tested by just increasing the version. All Cluster Issuers and Cluster Roles should still exist and be updated.
Configmap Upgrade can be tested with the reproducer mentioned on the ticket
Ingress update should be tested with
2-01_try-now(subdomain based) and2-03_try-now_paths(path based) test-configurations.instances-ingress-path-based.yamlandinstances-ingress.yamle.g. increase thenginx.ingress.kubernetes.io/proxy-buffer-sizeslightly and update the helm chart versionterraform applyagain with new chart. Verify that the changed value in the ingress has changedBase chart upgrade can be tested by just increasing the version. All Cluster Issuers and Cluster Roles should still exist and be updated.
Configmap Upgrade can be tested with the reproducer mentioned on the ticket