[stable/anchore-engine] Installing in Kuebrenete 1.16

[allupaku]

Describe the bug
Trying to install the chart, it stops by spitting out error message

Error: validation failed: unable to recognize "": no matches for kind "Deployment" in version "extensions/v1beta1"

Version of Helm and Kubernetes:
Kuebrnetes : 1.6
Helm : 2.15.2

Which chart:
stable/anchore-engine

What happened:
Installation Stopped

What you expected to happen:
Installation of anchore engine to succeed

How to reproduce it (as minimally and precisely as possible):
Install it in kubernetes using helm and inside a custom namespace

Anything else we need to know:
I am trying to install it in a custom namespace.

[zhill]

Thanks @allupaku. This is a known issue we'll be resolving shortly. Thanks!

[tholu]

Same problem here with stable/prometheus.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[Btodhunter]

@allupaku This issue is due to our dependency on the postgresql v1.0.0 chart. We've had a lot of discussion about upgrading the chart and have decided to hold off on that upgrade until we migrate our chart to our own official chart repository which will be available on the Helm Hub. We made this decision because the upgrade path from v1.0.0 of the postgresql was quite extensive and we didn't want to cause upgrade issues for users with current running deployments.

You can track progress of the migration to Helm Hub and updating of the postgresql chart here

[L0g4n]

I am also facing this problem would appreciate a fix.

[mattjnewberry]

Same issue, following the issue resolving it. Is there an ETA on the fix or a could you please suggest a workaround if possible? Thanks!

[Btodhunter]

@mattjnewberry a quick workaround (which isn't exactly ideal, but it works) is to do helm pull --untar stable/anchore-engine && sed -i 's#extensions/v1beta1#apps/v1#g' ./anchore-engine/charts/postgresql/templates/deployment.yaml && helm install anchore ./anchore-engine

That will update the postgresql deployment template to use apps/v1 and make it compatible with kubernetes 1.16 - the downside being that you're deploying from a local chart rather then directly from the stable repo.

[L0g4n]

@Btodhunter I am gonna try this workaround later and report back if its working for me (i got a raspberry pi 4 as a master, so i additionally need to add amd64 node selctors). Anyway, thanks for your answer.

[L0g4n]

@Btodhunter I am facing the issue that on all pods the readiness and livenes probes failed, as it seems the pods are unable to reach each other via the specified ports:

Events:
Normal Scheduled default-scheduler Successfully assigned default/ae-anchore-engine-api-7d57cdd58b-9s8wl to debian-buster-vm
Normal Pulled 11m kubelet, debian-buster-vm Container image >"docker.io/anchore/anchore-engine:v0.6.1" already present on machine
Normal Created 11m kubelet, debian-buster-vm Created container anchore-engine-api
Normal Started 11m kubelet, debian-buster-vm Started container anchore-engine-api
Warning Unhealthy 8m57s (x5 over 9m37s) kubelet, debian-buster-vm Liveness probe failed: Get > http://10.42.1.80:8228/health: dial tcp 10.42.1.80:8228: connect: connection refused
Warning Unhealthy 95s (x61 over 11m) kubelet, debian-buster-vm Readiness probe failed: Get http://10.42.1.80:8228/health: dial tcp 10.42.1.80:8228: connect: connection refused

My exact problem is this one: https://devops.stackexchange.com/questions/8307/deploying-anchore-to-kubernetes-cluster-using-helm

Do you happen to know what causes this problem? This post says that the postgresql database chart may be misconfigured.

Edit: Okay, I managed to get it working that way. It seemed that was a problem with DNS resolving and some iptables rules on my k3s cluster.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[cityofships]

Related: #18648

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[frittentheke]

This is not stale

[swapnilpotnis]

I tend to agree with @frittentheke . the issue still occcurs with the latest release of anchore-engine.

[ftcreator]

Is there any fix for this. Please let us know

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[danoliver1]

This is not stale.

[zhill]

We're working on this in our own chart repo and will be registering that in helm hub.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[tholu]

Likely not stale.

[Btodhunter]

A new chart version 1.7.0 is now available on our charts repo at https://charts.anchore.io that is compatible with k8s v1.15+

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[stale]

This issue is being automatically closed due to inactivity.