With the latest pulumi CLI version 3.22.0 which was released today, we have problems in K8s deployments after pulumi CLI upgrade when we have apps with the environment variables of type integer in your stack yaml file which must be treated as string during pulumi update. It actually coverts them back to integer typed values instead of string typed values. To give an example, we have an app containing the following environment variables whose values must be of type string

secretsprovider: azurekeyvault://************
encryptedkey: ******
config:
  azure:clientId: ************
  azure:clientSecret:
    secure: **************************
  azure:environment: public
  azure:location: ***********
  azure:subscriptionId: ******************
  azure:tenantId: **********
  tre-se-api:container-env-variables:
   - name: SERVER_CACHE_TTL
     value: "10000"
   - name: CACHE_TTL
     value: "10"
   - name: CACHE_CHECK_PERIOD
     value: "60"

When we do

pulumi up

, it changes the above stack config as below,

secretsprovider: azurekeyvault://************
encryptedkey: ******
config:
  azure:clientId: ************
  azure:clientSecret:
    secure: **************************
  azure:environment: public
  azure:location: ***********
  azure:subscriptionId: ******************
  azure:tenantId: **********
  tre-se-api:container-env-variables:
   - name: SERVER_CACHE_TTL
     value: 10000
   - name: CACHE_TTL
     value: 10
   - name: CACHE_CHECK_PERIOD
     value: 60

Due to the change of stack config, we get

cannot convert int64 to string

problem. Solution: we needed to go back to the previous version(v3.21.2) to solve this problem.