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/03/10 08:40:23 UTC
[GitHub] [apisix-ingress-controller] tb51cx opened a new issue #917: request help: apisix-ingress-controller一直初始化
tb51cx opened a new issue #917:
URL: https://github.com/apache/apisix-ingress-controller/issues/917
### Issue description
helm安装命令如下
helm install apisix-ingress-controller apisix/apisix-ingress-controller \
--set gateway.type=NodePort \
--set ingress-controller.enabled=true \
--namespace ingress-apisix \
--set ingress-controller.config.apisix.serviceNamespace=ingress-apisix \
--set etcd.enabled=false \
--set etcd.auth.tls.enabled=true \
--set etcd.host={https://172.18.188.205:2379\,https://172.18.188.206:2379\,https://172.18.188.208:2379} \
--set etcd.auth.tls.existingSecret=etcd-ssl \
--set etcd.auth.tls.certFilename=tls.crt \
--set etcd.auth.tls.certKeyFilename=tls.key \
--set etcd.auth.tls.verify=false
kubectl describe deployment apisix-ingress-controller -n ingress-apisix
Name: apisix-ingress-controller
Namespace: ingress-apisix
CreationTimestamp: Thu, 10 Mar 2022 16:20:35 +0800
Labels: app.kubernetes.io/instance=apisix-ingress-controller
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=apisix-ingress-controller
app.kubernetes.io/version=1.4.0
helm.sh/chart=apisix-ingress-controller-0.9.0
Annotations: deployment.kubernetes.io/revision: 1
meta.helm.sh/release-name: apisix-ingress-controller
meta.helm.sh/release-namespace: ingress-apisix
Selector: app.kubernetes.io/instance=apisix-ingress-controller,app.kubernetes.io/name=apisix-ingress-controller
Replicas: 1 desired | 1 updated | 1 total | 0 available | 1 unavailable
StrategyType: RollingUpdate
MinReadySeconds: 0
RollingUpdateStrategy: 25% max unavailable, 25% max surge
Pod Template:
Labels: app.kubernetes.io/instance=apisix-ingress-controller
app.kubernetes.io/name=apisix-ingress-controller
Annotations: checksum/config: bfb515474969488fea3ee7eaaf9f1848f22f7d65894ca6e5297ecd8db10eb4bb
Service Account: apisix-ingress-controller
Init Containers:
wait-apisix-admin:
Image: busybox:1.28
Port: <none>
Host Port: <none>
Command:
sh
-c
until nc -z apisix-admin.ingress-apisix.svc.cluster.local 9180 ; do echo waiting for apisix-admin; sleep 2; done;
Environment: <none>
Mounts: <none>
Containers:
apisix-ingress-controller:
Image: apache/apisix-ingress-controller:1.4.0
Port: 8080/TCP
Host Port: 0/TCP
Command:
/ingress-apisix/apisix-ingress-controller
ingress
--config-path
/ingress-apisix/conf/config.yaml
Liveness: http-get http://:8080/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
Readiness: http-get http://:8080/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
Environment:
POD_NAMESPACE: (v1:metadata.namespace)
POD_NAME: (v1:metadata.name)
Mounts:
/ingress-apisix/conf from configuration (rw)
Volumes:
configuration:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: apisix-ingress-controller-configmap
Optional: false
Conditions:
Type Status Reason
---- ------ ------
Available False MinimumReplicasUnavailable
Progressing False ProgressDeadlineExceeded
OldReplicaSets: <none>
NewReplicaSet: apisix-ingress-controller-5b89f5c67b (1/1 replicas created)
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal ScalingReplicaSet 16m deployment-controller Scaled up replica set apisix-ingress-controller-5b89f5c67b to 1
kubectl get pod -n ingress-apisix
NAME READY STATUS RESTARTS AGE
apisix-ingress-controller-5b89f5c67b-hcprv 0/1 Init:0/1 0 17m
kubectl describe pod apisix-ingress-controller-5b89f5c67b-hcprv -n ingress-apisix
Name: apisix-ingress-controller-5b89f5c67b-hcprv
Namespace: ingress-apisix
Priority: 0
Node: 172.18.188.205/172.18.188.205
Start Time: Thu, 10 Mar 2022 16:20:36 +0800
Labels: app.kubernetes.io/instance=apisix-ingress-controller
app.kubernetes.io/name=apisix-ingress-controller
pod-template-hash=5b89f5c67b
Annotations: checksum/config: bfb515474969488fea3ee7eaaf9f1848f22f7d65894ca6e5297ecd8db10eb4bb
Status: Pending
IP: 172.20.90.162
IPs:
IP: 172.20.90.162
Controlled By: ReplicaSet/apisix-ingress-controller-5b89f5c67b
Init Containers:
wait-apisix-admin:
Container ID: containerd://c8392e2bdb7576668372355ab9d589435f729ef52883aaebf34a9e90d4f91a5f
Image: busybox:1.28
Image ID: docker.io/library/busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47
Port: <none>
Host Port: <none>
Command:
sh
-c
until nc -z apisix-admin.ingress-apisix.svc.cluster.local 9180 ; do echo waiting for apisix-admin; sleep 2; done;
State: Running
Started: Thu, 10 Mar 2022 16:20:36 +0800
Ready: False
Restart Count: 0
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-vpd7r (ro)
Containers:
apisix-ingress-controller:
Container ID:
Image: apache/apisix-ingress-controller:1.4.0
Image ID:
Port: 8080/TCP
Host Port: 0/TCP
Command:
/ingress-apisix/apisix-ingress-controller
ingress
--config-path
/ingress-apisix/conf/config.yaml
State: Waiting
Reason: PodInitializing
Ready: False
Restart Count: 0
Liveness: http-get http://:8080/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
Readiness: http-get http://:8080/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
Environment:
POD_NAMESPACE: ingress-apisix (v1:metadata.namespace)
POD_NAME: apisix-ingress-controller-5b89f5c67b-hcprv (v1:metadata.name)
Mounts:
/ingress-apisix/conf from configuration (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-vpd7r (ro)
Conditions:
Type Status
Initialized False
Ready False
ContainersReady False
PodScheduled True
Volumes:
configuration:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: apisix-ingress-controller-configmap
Optional: false
kube-api-access-vpd7r:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 17m default-scheduler Successfully assigned ingress-apisix/apisix-ingress-controller-5b89f5c67b-hcprv to 172.18.188.205
Normal Pulled 17m kubelet Container image "busybox:1.28" already present on machine
Normal Created 17m kubelet Created container wait-apisix-admin
Normal Started 17m kubelet Started container wait-apisix-admin
### Environment
- your apisix-ingress-controller version (output of apisix-ingress-controller version --long):
- your Kubernetes cluster version (output of kubectl version):
- if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a):
--
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-ingress-controller] tb51cx commented on issue #917: request help: apisix-ingress-controller一直初始化
Posted by GitBox <gi...@apache.org>.
tb51cx commented on issue #917:
URL: https://github.com/apache/apisix-ingress-controller/issues/917#issuecomment-1063848979
kubectl logs -f apisix-ingress-controller-5b89f5c67b-hcprv -c wait-apisix-admin -n ingress-apisix
waiting for apisix-admin
nc: bad address 'apisix-admin.ingress-apisix.svc.cluster.local'
--
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