Closed lou-lan closed 11 months ago
When I tried again, I found that I wouldn't create domain-mapping deployment again. Did it happen that the file serving-core.yaml was updated?
The domain-mapping deployment no longer exists, it was integrated with the existing Serving controller in 1.11: https://github.com/knative/serving/releases/tag/knative-v1.11.0.
Make sure to remove old resources when you install a new version. With the YAML installation method, it is not possible to do this automatically.
The domain-mapping deployment no longer exists, it was integrated with the existing Serving controller in 1.11: https://github.com/knative/serving/releases/tag/knative-v1.11.0.
Make sure to remove old resources when you install a new version. With the YAML installation method, it is not possible to do this automatically.
Thanks
Expected Behavior
All pods to Running.
Actual Behavior
Steps to Reproduce the Problem
kubectl apply -f https://github.com/knative/serving/releases/download/knative-v1.12.2/serving-crds.yaml
kubectl apply -f https://github.com/knative/serving/releases/download/knative-v1.12.2/serving-core.yaml
kubectl get pods
Additional Info
Additional context
I have observed that the kubectl command is using
v1beta1/domainmappings
, while the poddomain-mapping
is requestingv1alpha1/domainmappings
.Install information:
self-building
v1.12.2