Skip to main content
Solved

Upgrading Kasten above 5.0.10 using Helm is generating the error with the GarbageCollector image

J

Hello support,

 

We’ve tried to upgrade Kasten from 5.0.10 to 5.5.2 as suggested by the Setting interface page.

 

When applying the command

helm repo update && \
    helm get values k10 --output yaml --namespace=kasten-io > k10_val.yaml && \
    helm upgrade k10 kasten/k10 --namespace=kasten-io -f k10_val.yaml --version=5.5.2

 

The upgrade throw the following error:
Error: UPGRADE FAILED: cannot patch "crypto-svc" with kind Deployment: Deployment.apps "crypto-svc" is invalid: spec.template.spec.containers[3].image: Required value

 

When looking at the helm manifest using the command “helm get manifest k10”, we saw that the garbagecollector-svc introduced in 5.0.11 didn’t have an image:

 

We’ve tried to perform an upgrade to 5.0.11 and to 5.5.1 to try escaping from this issue, we even perform another upgrade to 5.0.10 to regenerate the manifests but none of these solutions worked.

 

Can you please help?

 

Thank you very much in advance !

Best answer by FRubens

Hello @JCandela 

Thank you for the values file.

Please would you confirm if you are using K10 Operator install ?

I am asking this, because your K10 values file has some global images setup that usually is seem on operator installations, you might have to due some clean up in you values file, there are duplicate entries for global images and the one that has the images is missing garbagecollector as an example, that might point to the error you were seeing.

##Part of the file were the images are, there are more than one entry for the same values in your file
global:
  airgapped:
    repository: ""
  imagePullSecret: ""
  images:
    admin: registry.connect.redhat.com/kasten/admin@sha256:7046bc543e815d48011af8028cb57645c7e3a78647f9e21047ad5ab41e9aa2b7
    aggregatedapis: registry.connect.redhat.com/kasten/aggregatedapis@sha256:e1af0cdfda0a82e4e7fdcb2d99169df97398a26cfaa96174bb13dcbf4686bd62
    ambassador: ""

Would be good to remove the Global images section, but still we recommend using only the values you need instead of having entire K10 values list in the file, and since this file has duplicate entries, would be necessary to clean it, and keep only the values you need.

Make a backup copy of the file and do the changes.

After cleaning up your K10 values file please re-try the upgrade and let us know.

Regards
FRubens

View original
Did this topic help you find an answer to your question?

9 comments

J
  • JCandela
  • Author
  • New Here
  • 6 comments
  • April 21, 2023

Here is the error within the k10 helm manifest:

 

 

Chris.Childerhose
FRubens
2 people like this
  • Chris.Childerhose
    Chris.Childerhose
  • FRubens
    FRubens
jaiganeshjk
Forum|alt.badge.img+2
  • jaiganeshjk
  • Experienced User
  • 275 comments
  • April 21, 2023

@JCandela Thanks for posting your question here.

 

Would you be able to share the values file that you have ? (Please redact any sensitive info in it)

Jaiganesh
Chris.Childerhose
FRubens
2 people like this
  • Chris.Childerhose
    Chris.Childerhose
  • FRubens
    FRubens
FRubens
Forum|alt.badge.img+2
  • FRubens
  • Experienced User
  • 96 comments
  • April 21, 2023

Hello @JCandela ,

Thank you for using our community and K10!

I am checking this and will update soon.

FRubens

Chris.Childerhose
1 person likes this
  • Chris.Childerhose
    Chris.Childerhose
J
  • JCandela
  • Author
  • New Here
  • 6 comments
  • April 21, 2023
jaiganeshjk wrote:

@JCandela Thanks for posting your question here.

 

Would you be able to share the values file that you have ? (Please redact any sensitive info in it)

Please find below the k10_val.yaml (with all the sensitive information masked):

https://pastebin.com/eDJ4Huai

Chris.Childerhose
FRubens
2 people like this
  • Chris.Childerhose
    Chris.Childerhose
  • FRubens
    FRubens
FRubens
Forum|alt.badge.img+2
  • FRubens
  • Experienced User
  • 96 comments
  • April 21, 2023

@JCandela ,

 

Please could you check the permissions to the link you provided, it is private denying access.

 

Thank you

Fernando

Chris.Childerhose
1 person likes this
  • Chris.Childerhose
    Chris.Childerhose
J
  • JCandela
  • Author
  • New Here
  • 6 comments
  • April 21, 2023
FRubens wrote:

@JCandela ,

 

Please could you check the permissions to the link you provided, it is private denying access.

 

Thank you

Fernando

Sorry for the miss, permissions has been fixed, the password is “kasten” (without the quotes).

https://pastebin.com/eDJ4Huai

Chris.Childerhose
FRubens
2 people like this
  • Chris.Childerhose
    Chris.Childerhose
  • FRubens
    FRubens
FRubens
Forum|alt.badge.img+2
  • FRubens
  • Experienced User
  • 96 comments
  • Answer
  • April 21, 2023

Hello @JCandela 

Thank you for the values file.

Please would you confirm if you are using K10 Operator install ?

I am asking this, because your K10 values file has some global images setup that usually is seem on operator installations, you might have to due some clean up in you values file, there are duplicate entries for global images and the one that has the images is missing garbagecollector as an example, that might point to the error you were seeing.

##Part of the file were the images are, there are more than one entry for the same values in your file
global:
  airgapped:
    repository: ""
  imagePullSecret: ""
  images:
    admin: registry.connect.redhat.com/kasten/admin@sha256:7046bc543e815d48011af8028cb57645c7e3a78647f9e21047ad5ab41e9aa2b7
    aggregatedapis: registry.connect.redhat.com/kasten/aggregatedapis@sha256:e1af0cdfda0a82e4e7fdcb2d99169df97398a26cfaa96174bb13dcbf4686bd62
    ambassador: ""

Would be good to remove the Global images section, but still we recommend using only the values you need instead of having entire K10 values list in the file, and since this file has duplicate entries, would be necessary to clean it, and keep only the values you need.

Make a backup copy of the file and do the changes.

After cleaning up your K10 values file please re-try the upgrade and let us know.

Regards
FRubens

J
  • JCandela
  • Author
  • New Here
  • 6 comments
  • April 21, 2023

I was using Openshift Operator but when we upgraded our cluster from 4.7 to 4.10, the Openshift Operator was not able to be upgraded because of API deprecations.

 

So we moved to helm to upgrade Kasten and then come back to the Openshift Operator.

 

If I clean the K10 values in the file, would I be able to move from Helm to Openshift Operator again?

jaiganeshjk
FRubens
2 people like this
  • jaiganeshjk
    jaiganeshjk
  • FRubens
    FRubens
J
  • JCandela
  • Author
  • New Here
  • 6 comments
  • April 24, 2023

Hello @FRubens,

 

After removing the “global” section, the upgrade works, thanks you very much !

jaiganeshjk
FRubens
2 people like this
  • jaiganeshjk
    jaiganeshjk
  • FRubens
    FRubens

Comment


Terms & Conditions