-
Bug
-
Resolution: Done
-
Critical
-
v0.7.0
-
None
-
None
-
Serverless Sprint 169
When installing the knative serving operator 0.7.1 on a cluster with Maistra 0.11 pre-installed, the v1beta1.custom.metrics.k8s.io APIService is broken
(using OCP 4.1.4 on AWS)
apiVersion: apiregistration.k8s.io/v1
kind: APIService
metadata:
annotations:
manifestival: new
creationTimestamp: "2019-07-11T06:53:42Z"
labels:
autoscaling.knative.dev/metric-provider: custom-metrics
serving.knative.dev/release: devel
name: v1beta1.custom.metrics.k8s.io
resourceVersion: "23263"
selfLink: /apis/apiregistration.k8s.io/v1/apiservices/v1beta1.custom.metrics.k8s.io
uid: 9eb0b0c4-a3a8-11e9-9385-0287d8e79c22
spec:
group: custom.metrics.k8s.io
groupPriorityMinimum: 100
insecureSkipTLSVerify: true
service:
name: autoscaler
namespace: knative-serving
version: v1beta1
versionPriority: 100
status:
conditions:
- lastTransitionTime: "2019-07-11T06:53:42Z"
message: 'no response from https://10.130.2.12:8443: Get https://10.130.2.12:8443:
remote error: tls: handshake failure'
reason: FailedDiscoveryCheck
status: "False"
type: Available
$ oc get endpoints --all-namespaces | grep 10.130.2.12 knative-serving autoscaler 10.130.2.12:9090,10.130.2.12:8443,10.130.2.12:8080 3m39s
A broken APIService on a cluster causes varius issues on the cluster (like namespaces being stuck in Terminating state)