BUG: sealos fails to install with error validating "manifests/secret.yaml

[jizusun]

BUG: sealos fails to install with error validating "manifests/secret.yaml

[jizusun]

@lingdie Now there is an error (error when creating "manifests/deploy.yaml": ) before applying the secret!

$ sealos pull  registry.cn-shanghai.aliyuncs.com/labring/sealos-cloud:latest
051115c32df50c8a3b0102d1918f606efde52dfff85101180396d16d765da24d

$ sealos reset

$ curl -sfL https://raw.githubusercontent.com/labring/sealos/main/scripts/cloud/install.sh -o install.sh && \
  bash -x install.sh \
  --single \
  --image-registry=registry.cn-shanghai.aliyuncs.com --zh \
  --cloud-domain=130.147.249.243.nip.io \
  --cloud-port=443 


+ kubectl apply -f manifests/deploy.yaml -f manifests/rbac.yaml -f manifests/ingress.yaml
serviceaccount/desktop-frontend unchanged
service/desktop-frontend unchanged
configmap/desktop-frontend-config unchanged
clusterrole.rbac.authorization.k8s.io/auth-system-manager-role unchanged
clusterrolebinding.rbac.authorization.k8s.io/desktop-user-editor-role-binding unchanged
clusterrolebinding.rbac.authorization.k8s.io/desktop-operationrequest-editor-role-binding unchanged
clusterrolebinding.rbac.authorization.k8s.io/desktop-deleterequest-editor-role-binding unchanged
role.rbac.authorization.k8s.io/recharge-gift-cm-reader unchanged
rolebinding.rbac.authorization.k8s.io/recharge-gift-cm-reader-rolebinding unchanged
clusterrole.rbac.authorization.k8s.io/account-editor-role unchanged
clusterrolebinding.rbac.authorization.k8s.io/desktop-account-editor-role-binding unchanged
ingress.networking.k8s.io/sealos-desktop unchanged
Error from server (BadRequest): error when creating "manifests/deploy.yaml": Deployment in version "v1" cannot be handled as a Deployment: json: cannot unmarshal bool into Go struct field EnvVar.spec.template.spec.containers.env.value of type string
Error: exit status 1
Error: exit status 1

[lingdie]

Sry for that, this two pr will fix: #4547 #4544

Please retry later after latest image build.

Or you can use the stable version: v5.0.0-beta4.

v5.0.0-beta5 will release in this two weeks.

[jizusun]

@lingdie

Thank you so much! Now the installation is successfull!
Close the issue.

[jizusun]

But I found the workaround doesn't work, since some values like mongo-url is missing.

Anybody can guide me?

---

Okay, finally I found a workaround, that is after the exit,

I manually apply the secret with

  kubectl apply -f manifests/secret.yaml --validation=false

I'm wondering if we need to fix this line

sealos/frontend/desktop/deploy/scripts/init.sh

Line 12 in ae7d7ed

kubectl apply -f manifests/secret.yaml

[lingdie]

This pr shell fix it.

#4545

[jizusun]

@lingdie Thank you for your PR and I see it's merged.
I pulled the latest image

sealos pull  registry.cn-shanghai.aliyuncs.com/labring/sealos-cloud:latest
41033415b58a06b5cf1afca2ed16a8f6f19d6164be07395776c4ba212db5c7df

Then I do

sealos reset

curl -sfL https://raw.githubusercontent.com/labring/sealos/main/scripts/cloud/install.sh -o install.sh && \
  bash -x install.sh \
  --image-registry=registry.cn-shanghai.aliyuncs.com --zh \
  --cloud-domain=130.147.249.243.nip.io \
  --cloud-port=443 

But still the same error

create desktop secret
+ kubectl apply -f manifests/secret.yaml
error: error validating "manifests/secret.yaml": error validating data: [unknown object type "nil" in Secret.data.ali_access_key_id, unknown object type "nil" in Secret.data.ali_access_key_secret, unknown object type "nil" in Secret.data.ali_sms_endpoint, unknown object type "nil" in Secret.data.ali_sms_sign_name, unknown object type "nil" in Secret.data.ali_sms_template_code, unknown object type "nil" in Secret.data.github_client_id, unknown object type "nil" in Secret.data.github_client_secret, unknown object type "nil" in Secret.data.wechat_client_id, unknown object type "nil" in Secret.data.wechat_client_secret]; if you choose to ignore these errors, turn validation off with --validate=false
Error: exit status 1
Error: exit status 1

How can I verify the fix is included in the latest image?

[lingdie]

try use this image:

sealos pull --policy=always docker.io/labring/sealos-cloud:latest
sealos tag docker.io/labring/sealos-cloud:latest registry.cn-shanghai.aliyuncs.com/labring/sealos-cloud:latest

image id: 051115c32df50c8a3b0102d1918f606efde52dfff85101180396d16d765da24d

[jizusun]

Thank you so much for the quick fix! @lingdie
I'm wondering what's the image tag of docker.io/labring/sealos-cloud:latest after your #4547
Can you guide me how to check? (Should be in the GitHub Actions workflow log?)

[lingdie]

try this:

sealos pull --policy=always docker.io/labring/sealos-cloud:latest
sealos tag docker.io/labring/sealos-cloud:latest registry.cn-shanghai.aliyuncs.com/labring/sealos-cloud:latest

image id: 7231c418dc856d4c2290477fd9b3da7b0e3a9eea51d34f3e77bc356a57074dc8

[lingdie]

run after reset?