apigee-controller-manager pods

[shayan]

kubectl get pods -n apigee-system


apigee-controller-manager-6dbb9fb8df-dpxjg 1/2 CrashLoopBackOff

Guy's please give solution

[Hilda_Arteaga]

Hi @shayan 

Thanks for sharing your inquiry in the Apigee forum. In order to better assist you. Could you please provide more details of what exactly assistance you are looking for?

In the meantime we can share with you that this kind of failure is usually related to the following:

1. Connectivity failure between apigee-controller-manager and Kubernetes API server. 

Beside the connectivity failure, this could mean that the API server can be dead or malfunctioning

Possible Solution: Fix network connectivity failure between apigee-controller-manager pods and the Kubernetes API server, then ensure that Kubernetes API server is up and running.

• A possibility of Misconfigured/deleted apigee-manager service account.

Possible Solution: You can reconfigure the appige-manager service account by running the following commands: “Helm” or “apigeectl”

We look forward to your comments, and we hope this information is helpful

[shayan]

Hi,

Thanks for your response.

1: API server is working fine. 
2: no issue with the service account.

Still facing the same issue.

[omidt]

Have you tried kubectl describe on the pod to find any logs or events relating to the workload?

Please also state which version of Apigee hybrid you have installed and on which Kubernetes distribution/platform.

[jphoga]

Hi Shayan,

The issue you are describing can have a variety of root causes and it is very hard to give advise without additional data and especially the logs from the controller manager pod. 

I propose to do the following:

1. Collect the Hybrid must-gather data by running the commands on this page for your impacted cluster.

2. Open a support case in the Google Cloud Support Portal, describe the issue you are facing in great detail and attach the above collect Hybrid must-gather data to the case.

Thanks