fix(cloud-native): wrong agama configuration in default config

[mzico]

Flex latest nightly build ( Oct 22, 2025 )
Check out this video below, it's not loading "default configuration" in "casa" Agama-flow.
Which is breaking jans-casa login after 2FA activation.

Screencast.From.2025-10-22.18-53-59.webm

Here is how it should work ( it's working in VM based Flex installation ):

• Default installation should include out-of-the-box config to load jans-casa properly. As you can see in below video that.. whenever I am trying to use "Export Configuration", it's downloading default config as json.
• This is not happening for Cloud Native Edition ( recorded video above ).

Screencast.From.2025-10-22.20-54-02.webm

[iromli]

@duttarnab from first video, there's popup saying No configurations defined for casa. Which configuration does admin-ui refer to?

[duttarnab]

Hi @iromli

After deploying Agama projects on the Auth Server, you may need to provide configuration properties for the flows if required by the projects. This is done by clicking “Export the sample config” button to download sample configuration file for the project, making necessary changes in the sample configuration, and then using “Import configuration”. Once imported, “Export current configuration” allows you to download the current configuration.

Note: In the Casa Agama project deployed on the VM Flex installation, the current configuration is available by default. However, in the CN installation, it shows “No configurations defined for Casa.”

cc: @jgomer2001

[iromli]

hi @duttarnab

After you pointed out about properties in agmFlow.agFlowMeta column, I found out 2 scenarios:

1. casa and/or auth-server pods restarted several times before fully ready.

   In this scenario, the agmFlow.agFlowMeta properties is null for each entry. My guess is that properties is not being loaded properly or halted during restarts.

2. casa and/or auth-server pods not having restarts.

   The properties of agmFlow.agFlowMeta is loaded properly for each entry.

I'm testing the 2nd scenario by increasing the default failureThreshold of k8s' readinessProbe and livenessProbe attributes.