jeho

Since the schema changes are quite complex, the values migration is not straight forward. We still need to implement it.

Hey team! Please [add your planning poker estimate](https://app.zenhub.com/workspaces/DEV-5e7e84dddc966f05a627a19b/issues/redkubes/otomi-core/1502?planning-poker) with Zenhub @Ani1357 @dennisvankekem @ElderMatt @ferruhcihan @merll

@ElderMatt does it mean we cannot control it?

yes, from the screencast you were looking at platform pass, whereas you should look at team apps.

Hey team! Please [add your planning poker estimate](https://app.zenhub.com/workspaces/DEV-5e7e84dddc966f05a627a19b/issues/redkubes/otomi-core/1479?planning-poker) with Zenhub @Ani1357 @dennisvankekem @ElderMatt @ferruhcihan @merll

The proposed solution is to read content of existing secrets (for each secret defined in each team), then create SealedSecret out of it and deploy it. Next is to change...

There is a problem with secret type that is immutable. Legacy secret type is `opaque`. However SealedSecrets is using the new type: `kubernetes.io/opaque`. Having that, a given secret needs to...

well done

Hey team! Please [add your planning poker estimate](https://app.zenhub.com/workspaces/DEV-5e7e84dddc966f05a627a19b/issues/redkubes/otomi-core/1338?planning-poker) with Zenhub @Ani1357 @dennisvankekem @ElderMatt @ferruhcihan @staticvoid255

Hey team! Please [add your planning poker estimate](https://app.zenhub.com/workspaces/DEV-5e7e84dddc966f05a627a19b/issues/redkubes/otomi-core/1329?planning-poker) with Zenhub @Ani1357 @dennisvankekem @ElderMatt @ferruhcihan @staticvoid255