You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/04/07 08:38:57 UTC

[GitHub] [apisix-helm-chart] DwGoing opened a new issue, #263: apisix-ingress-controller is always PodInitializing

DwGoing opened a new issue, #263:
URL: https://github.com/apache/apisix-helm-chart/issues/263

   When i used Helm to install APISIX and set ingress-controller enabled, the pod of apisix-ingress-controller was always PodInitializing.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-helm-chart] tokers commented on issue #263: apisix-ingress-controller is always PodInitializing

Posted by GitBox <gi...@apache.org>.
tokers commented on issue #263:
URL: https://github.com/apache/apisix-helm-chart/issues/263#issuecomment-1091527353

   The init container in the pod will check the reachability of apisix cluster (admin api), see https://github.com/apache/apisix-helm-chart/blob/master/charts/apisix-ingress-controller/templates/deployment.yaml#L54 for details. Make sure your APISIX cluster is ready.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-helm-chart] DwGoing commented on issue #263: apisix-ingress-controller is always PodInitializing

Posted by GitBox <gi...@apache.org>.
DwGoing commented on issue #263:
URL: https://github.com/apache/apisix-helm-chart/issues/263#issuecomment-1091329609

   Log shows "Error from server (BadRequest): container "ingress-controller" in pod "apisix-ingress-controller-cb5df4b7b-47wpq" is waiting to start: PodInitializing".


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-helm-chart] DwGoing commented on issue #263: apisix-ingress-controller is always PodInitializing

Posted by GitBox <gi...@apache.org>.
DwGoing commented on issue #263:
URL: https://github.com/apache/apisix-helm-chart/issues/263#issuecomment-1091552344

   <img width="845" alt="image" src="https://user-images.githubusercontent.com/16076018/162180750-c05ba21e-fe08-4be2-a636-ed1d6d5c3a6a.png">
   I don't know is it ok. Only apisix-ingress-controller is not ready, and i can use apisix-dashboard.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-helm-chart] DwGoing commented on issue #263: apisix-ingress-controller is always PodInitializing

Posted by GitBox <gi...@apache.org>.
DwGoing commented on issue #263:
URL: https://github.com/apache/apisix-helm-chart/issues/263#issuecomment-1092420729

   @tao12345666333 I sloved the problam!
   I have to configurate 'serviceNamespace' when the ns of apisix is not 'ingress-apisix'.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-helm-chart] DwGoing commented on issue #263: apisix-ingress-controller is always PodInitializing

Posted by GitBox <gi...@apache.org>.
DwGoing commented on issue #263:
URL: https://github.com/apache/apisix-helm-chart/issues/263#issuecomment-1092335356

   It's the Deployment of APISIX Ingress Controller. @tokers 
   ``` shell
   apiVersion: apps/v1
   kind: Deployment
   metadata:
     annotations:
       deployment.kubernetes.io/revision: "1"
       meta.helm.sh/release-name: apisix
       meta.helm.sh/release-namespace: apisix
     creationTimestamp: "2022-04-07T10:50:29Z"
     generation: 1
     labels:
       app.kubernetes.io/instance: apisix
       app.kubernetes.io/managed-by: Helm
       app.kubernetes.io/name: ingress-controller
       app.kubernetes.io/version: 1.4.0
       helm.sh/chart: ingress-controller-0.9.0
     name: apisix-ingress-controller
     namespace: apisix
     resourceVersion: "929126"
     uid: 85f759a2-f79f-4d67-b7fb-8b893011d546
   spec:
     progressDeadlineSeconds: 600
     replicas: 1
     revisionHistoryLimit: 10
     selector:
       matchLabels:
         app.kubernetes.io/instance: apisix
         app.kubernetes.io/name: ingress-controller
     strategy:
       rollingUpdate:
         maxSurge: 25%
         maxUnavailable: 25%
       type: RollingUpdate
     template:
       metadata:
         annotations:
           checksum/config: 7b1ee1030a34605149d9692d944bab499426de0718a0abcc3a157bb3ea1c4de3
         creationTimestamp: null
         labels:
           app.kubernetes.io/instance: apisix
           app.kubernetes.io/name: ingress-controller
       spec:
         containers:
         - command:
           - /ingress-apisix/apisix-ingress-controller
           - ingress
           - --config-path
           - /ingress-apisix/conf/config.yaml
           env:
           - name: POD_NAMESPACE
             valueFrom:
               fieldRef:
                 apiVersion: v1
                 fieldPath: metadata.namespace
           - name: POD_NAME
             valueFrom:
               fieldRef:
                 apiVersion: v1
                 fieldPath: metadata.name
           image: apache/apisix-ingress-controller:1.4.0
           imagePullPolicy: IfNotPresent
           livenessProbe:
             failureThreshold: 3
             httpGet:
               path: /healthz
               port: 8080
               scheme: HTTP
             periodSeconds: 10
             successThreshold: 1
             timeoutSeconds: 1
           name: ingress-controller
           ports:
           - containerPort: 8080
             name: http
             protocol: TCP
           readinessProbe:
             failureThreshold: 3
             httpGet:
               path: /healthz
               port: 8080
               scheme: HTTP
             periodSeconds: 10
             successThreshold: 1
             timeoutSeconds: 1
           resources: {}
           terminationMessagePath: /dev/termination-log
           terminationMessagePolicy: File
           volumeMounts:
           - mountPath: /ingress-apisix/conf
             name: configuration
         dnsPolicy: ClusterFirst
         initContainers:
         - command:
           - sh
           - -c
           - until nc -z apisix-admin.ingress-apisix.svc.cluster.local 9180 ; do echo
             waiting for apisix-admin; sleep 2; done;
           image: busybox:1.28
           imagePullPolicy: IfNotPresent
           name: wait-apisix-admin
           resources: {}
           terminationMessagePath: /dev/termination-log
           terminationMessagePolicy: File
         nodeSelector:
           node-role.kubernetes.io/master: ""
         restartPolicy: Always
         schedulerName: default-scheduler
         securityContext: {}
         serviceAccount: apisix-ingress-controller
         serviceAccountName: apisix-ingress-controller
         terminationGracePeriodSeconds: 30
         volumes:
         - configMap:
             defaultMode: 420
             items:
             - key: config.yaml
               path: config.yaml
             name: apisix-configmap
           name: configuration
   status:
     conditions:
     - lastTransitionTime: "2022-04-07T10:50:29Z"
       lastUpdateTime: "2022-04-07T10:50:29Z"
       message: Deployment does not have minimum availability.
       reason: MinimumReplicasUnavailable
       status: "False"
       type: Available
     - lastTransitionTime: "2022-04-07T11:00:30Z"
       lastUpdateTime: "2022-04-07T11:00:30Z"
       message: ReplicaSet "apisix-ingress-controller-59c659748f" has timed out progressing.
       reason: ProgressDeadlineExceeded
       status: "False"
       type: Progressing
     observedGeneration: 1
     replicas: 1
     unavailableReplicas: 1
     updatedReplicas: 1
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-helm-chart] tao12345666333 commented on issue #263: apisix-ingress-controller is always PodInitializing

Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #263:
URL: https://github.com/apache/apisix-helm-chart/issues/263#issuecomment-1092342030

   FYI https://github.com/apache/apisix-helm-chart/issues/252#issuecomment-1063862552


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-helm-chart] tokers commented on issue #263: apisix-ingress-controller is always PodInitializing

Posted by GitBox <gi...@apache.org>.
tokers commented on issue #263:
URL: https://github.com/apache/apisix-helm-chart/issues/263#issuecomment-1092330545

   > <img alt="image" width="845" src="https://user-images.githubusercontent.com/16076018/162180750-c05ba21e-fe08-4be2-a636-ed1d6d5c3a6a.png">
   > 
   > I don't know is it ok. Only apisix-ingress-controller is not ready, and i can use apisix-dashboard.
   
   @DwGoing Could you print the Deployment of APISIX Ingress Controller? Let's see the init container command, I have doubt about the address of apisix admin api.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-helm-chart] DwGoing closed issue #263: apisix-ingress-controller is always PodInitializing

Posted by GitBox <gi...@apache.org>.
DwGoing closed issue #263: apisix-ingress-controller is always PodInitializing
URL: https://github.com/apache/apisix-helm-chart/issues/263


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-helm-chart] DwGoing commented on issue #263: apisix-ingress-controller is always PodInitializing

Posted by GitBox <gi...@apache.org>.
DwGoing commented on issue #263:
URL: https://github.com/apache/apisix-helm-chart/issues/263#issuecomment-1091534866

   <img width="848" alt="image" src="https://user-images.githubusercontent.com/16076018/162179572-6b19b27a-c7ae-4970-8b75-847739999166.png">
   Is it ok?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org