Open nailushapotnuru opened 4 years ago
On Openshift, you might want to take a look at the Serverless operator that brings Knative pre-configured. See https://docs.openshift.com/container-platform/4.3/serverless/serverless-getting-started.html for more information.
Knative Serving otherwise isn't regularly build and tested on Openshift so there might be dragons.
That being said, the logs you shared don't contain the actual errors. Can you please fetch the logs of the containers to further debug (see the instructions given, you need to provide the respective container name)
Please find the pod logs below:
[cloud-user@ron5-bastion serving-operator]$ oc logs activator-7b4ccf8cc4-hmgtp Error from server (BadRequest): a container name must be specified for pod activator-7b4ccf8cc4-hmgtp, choose one of: [activator istio-proxy] or one of the init containers: [istio-init]
[cloud-user@ron5-bastion serving-operator]$ oc logs activator-7b4ccf8cc4-hmgtp -c istio-proxy Error from server (BadRequest): container "istio-proxy" in pod "activator-7b4ccf8cc4-hmgtp" is waiting to start: PodInitializing
When deploying serving-operator on Openshift 4.3, all the pods are failing with pod initialization error with status as 0/2 Init:crashloopbackofferror. Pre-req: Installed Istio using helm on OCP 4.3.
oc describe pod podname
![image](https://user-images.githubusercontent.com/28943483/80201527-e7500a00-8641-11ea-9e8c-6d6b3f1dff0b.png)
I have build images from- https://github.com/knative/serving/tree/v0.13.2 Istio version: 1.1.7