Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

For some reason, the UI is showing that I have an older version chart #409

Open
batazor opened this issue Mar 8, 2024 · 9 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@batazor
Copy link
Contributor

batazor commented Mar 8, 2024

Description

I'm using ArgoCD for updates, and have updated the chart many times, but at some point the chart version in the UI stopped updating and I always see the version - v1.17.3

I tried restarting the services, but apparently the result is cached somewhere in the configs?

Screenshot 2024-03-08 at 15 31 05

Environment

k8s 1.29

Steps To Reproduce

  1. Install old chart
  2. upgrade to new version

Expected behavior

correct version in UI

Actual Behavior

Additional context

@batazor batazor added the bug Something isn't working label Mar 8, 2024
@dwertent
Copy link
Contributor

Hi @batazor , are you sure the chart was updated?

Try running:

% helm list -n kubescape
NAME     	NAMESPACE	REVISION	UPDATED                             	STATUS  	CHART                    	APP VERSION
kubescape	kubescape	3       	2024-03-07 10:20:04.083042 +0200 IST	deployed	kubescape-operator-1.18.6	1.18.6

@batazor
Copy link
Contributor Author

batazor commented Mar 13, 2024

@dwertent

I use ArgoCD for installation/updating. And I see that I've the latest version of the images:

Screenshot 2024-03-13 at 12 48 21

In the end, it's not clear what could have gone wrong.

@dwertent
Copy link
Contributor

I noticed you enabled the release-upgrader during installation. However, if you are already managing it with argocd, enabling the release-upgrader is unnecessary. I think this might be the cause of the issue.

@batazor
Copy link
Contributor Author

batazor commented Mar 13, 2024

Disabled release-upgrader so far no results, maybe I should give time to synchronize all data with the cloud.

@dwertent
Copy link
Contributor

It should not take more than a few minutes.
Can you please contact me privately at dwertent@armosec.io so we can take a closer look into it? I would like to investigate based on your accountID.

@yuleib
Copy link
Contributor

yuleib commented Mar 17, 2024

@batazor - hey, do you have more then one cluster installed with this account ?

@batazor
Copy link
Contributor Author

batazor commented Mar 17, 2024

@yuleib I've re-created the cluster a couple of times in the last half a year, but I've used the same servers, so no artifacts should have survived.

Moreover, when I stopped kubescape, the metrics stopped coming, so I don't think that could be the reason.

As you can see from the dashboard, there were long phases when I didn't send metrics for various reasons
Screenshot 2024-03-17 at 15 25 56

@batazor
Copy link
Contributor Author

batazor commented Mar 17, 2024

Screenshot 2024-03-17 at 15 29 06 Screenshot 2024-03-17 at 15 30 23

And I don't see any other nodes or old resources as part of the cluster

@Oshratn
Copy link

Oshratn commented Aug 21, 2024

@batazor first of all I apologize the slow response.

From the screenshots this looks like an ARMO Platform, as such this is not the correct place to get support. Please try reaching via this link.

That being said, you might want to update the Helm chart to the latest and make sure that this is still not working as expected, since many versions of the Helm chart were released between your original request and today.

In addition, this issue has brought to light that there are many things in this support journey that still point to Kubescape. I will get the ARMO product team to make the necessary changes to avoid confusion in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants