Skip to content
This repository has been archived by the owner on Jun 24, 2020. It is now read-only.

Deploying serving-operator on Openshift4.3 #409

Open
nailushapotnuru opened this issue Apr 24, 2020 · 2 comments
Open

Deploying serving-operator on Openshift4.3 #409

nailushapotnuru opened this issue Apr 24, 2020 · 2 comments

Comments

@nailushapotnuru
Copy link

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.
image
oc describe pod podname
image

I have build images from- https://github.com/knative/serving/tree/v0.13.2
Istio version: 1.1.7

@markusthoemmes
Copy link
Contributor

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)

@nailushapotnuru
Copy link
Author

Please find the pod logs below:

image

[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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants