When installing karydia using the master branch, in the logs the factory.go tries to list resources "karydiasecuritypolicies", which results in an error as security policies got removed in the last commits.
E0520 08:50:06.838627 1 reflector.go:134] github.com/kinvolk/karydia/pkg/client/informers/externalversions/factory.go:117: Failed to list *v1alpha1.KarydiaSecurityPolicy: karydiasecuritypolicies.karydia.gardener.cloud is forbidden: User "system:serviceaccount:kube-system:karydia" cannot list resource "karydiasecuritypolicies" in API group "karydia.gardener.cloud" at the cluster scope
This is due to an old image karydia/karydia:0.1.0 that is used in the deployement.yaml. Instead, one should use the eu.gcr.io/gardener-project/karydia/karydia image (which is already used in the deployement-dev.yaml), which fixes this bug and should avoid similar problems in the future.
Description
When installing karydia using the master branch, in the logs the
factory.go
tries to list resources "karydiasecuritypolicies", which results in an error as security policies got removed in the last commits.This is due to an old image
karydia/karydia:0.1.0
that is used in the deployement.yaml. Instead, one should use theeu.gcr.io/gardener-project/karydia/karydia
image (which is already used in the deployement-dev.yaml), which fixes this bug and should avoid similar problems in the future.