)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":14394,"name":"Dale Smith","email":"dale@catalystcloud.nz","username":"dalees"},"change_message_id":"e9b09f6aa2557f72896c8268edc54eacc7521da5","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"1e1aa1ab_a2fa4384","updated":"2024-09-24 01:19:15.000000000","message":"I think this needs more discussion. Labels provided at cluster creation time could indeed override this with the proposed patchset, but then there is no supported way to change the helm chart version for the rest of the lifetime of the cluster?\n\nThis may leave you unable to upgrade to a new K8s version or CAPO version if the chart version is locked at something older (eg. v1alpha7 to v1beta1 resources).  Mutable labels would help here, but don\u0027t exist yet.\n\nFor our use case, we create curated Cluster Templates that combine a helm chart version and k8s version and these are what change when cluster upgrades are performed.","commit_id":"8ea0b78643a7010c4a54055e071b3ca4383007b0"},{"author":{"_account_id":8064,"name":"Jake Yip","email":"jake.yip@ardc.edu.au","username":"jake"},"change_message_id":"6c94790df737b04e967cbfa2fa1444de842e1a3d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"c0395617_d8c53484","in_reply_to":"1e1aa1ab_a2fa4384","updated":"2024-09-24 08:54:06.000000000","message":"Good point, your use case makes sense. Let\u0027s discuss in meeting.","commit_id":"8ea0b78643a7010c4a54055e071b3ca4383007b0"}]}