From 65f7d4ad66bcef3640c21bf87e6fa1ba1aeb2772 Mon Sep 17 00:00:00 2001 From: Alexey Kazakov Date: Mon, 5 May 2025 11:55:46 -0700 Subject: [PATCH 1/2] Add new registration-service config param for ui canary deployement --- .../toolchain.dev.openshift.com_toolchainconfigs.yaml | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/config/crd/bases/toolchain.dev.openshift.com_toolchainconfigs.yaml b/config/crd/bases/toolchain.dev.openshift.com_toolchainconfigs.yaml index 935482de9..a50dd1fed 100644 --- a/config/crd/bases/toolchain.dev.openshift.com_toolchainconfigs.yaml +++ b/config/crd/bases/toolchain.dev.openshift.com_toolchainconfigs.yaml @@ -235,6 +235,17 @@ spec: use for the registration service deployment format: int32 type: integer + uiCanaryDeploymentWeight: + description: |- + UICanaryDeploymentWeight specifies the threshold of users that will be using the new UI. + This configuration option is just a temporary solution for rolling out our new RHDH based UI using canary deployment strategy. + Once we switch all our users to the new UI this will be removed. + How this works: + - backend returns a weight + - old UI assigns a sticky random number for each user + - if the user has a number within the weight returned from the backend than user get's redirect to to new UI + - if the user has a number above the weight they keep using the current UI + type: integer verification: description: Keeps parameters necessary for the registration service verification config From a2b6d5678b9b629cdb6030cf2ab3fca7233705bb Mon Sep 17 00:00:00 2001 From: Alexey Kazakov Date: Tue, 6 May 2025 09:29:00 -0700 Subject: [PATCH 2/2] update --- .../bases/toolchain.dev.openshift.com_toolchainconfigs.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/config/crd/bases/toolchain.dev.openshift.com_toolchainconfigs.yaml b/config/crd/bases/toolchain.dev.openshift.com_toolchainconfigs.yaml index 9a0e0fe9e..f3a98d577 100644 --- a/config/crd/bases/toolchain.dev.openshift.com_toolchainconfigs.yaml +++ b/config/crd/bases/toolchain.dev.openshift.com_toolchainconfigs.yaml @@ -243,8 +243,10 @@ spec: How this works: - backend returns a weight - old UI assigns a sticky random number for each user - - if the user has a number within the weight returned from the backend than user get's redirect to to new UI + - if the user has a number within the weight returned from the backend than user get's redirect to new UI - if the user has a number above the weight they keep using the current UI + maximum: 100 + minimum: 0 type: integer verification: description: Keeps parameters necessary for the registration