keda conflict with ambassador

[aminebizid]

After installing Keda, Ambassador stop working.
The issue is cauded by v1beta1.custom.metrics.k8s.io
Ambassaor opened issue

apiVersion: apiregistration.k8s.io/v1beta1
kind: APIService
metadata:
  name: v1beta1.custom.metrics.k8s.io
spec:
  service:
    name: {{ template "keda.fullname" . }}
    namespace: {{ .Release.Namespace }}
  group: custom.metrics.k8s.io
  version: v1beta1
  insecureSkipTLSVerify: true
  groupPriorityMinimum: 100
  versionPriority: 100

as workaround to let ambassador works:

k -n keda delete apiservice v1beta1.custom.metrics.k8s.io

Why do we need custom.metrics in keda?

[jeffhollan]

Suspect it's the same issue as this one #90

[yamaszone]

Any update on this? We would like to give Keda a try but we use Ambassador and don't want to break it.

[jeffhollan]

@zroubalik is this related to #470 ?

[zroubalik]

@jeffhollan partially, as I can see, the problem is caused by missing APIService with name: v1beta1.custom.metrics.k8s.io currently we are usign name: v1beta1.external.metrics.k8s.io. Custom metrics are not implemented, we are using external.

Since the original issue is from May, I wonder if the problem is still relevant. It might be resolved since we are not using custom metrics.

[zroubalik]

@yamaszone @aminebizid do you still hitting this issue?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed due to inactivity.