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 2021/10/13 06:43:49 UTC
[GitHub] [apisix-ingress-controller] yingtxx removed a comment on issue #708: request help: Ingress 资源不同步 apisix
yingtxx removed a comment on issue #708:
URL: https://github.com/apache/apisix-ingress-controller/issues/708#issuecomment-941970639
install by apisix-helm-chart
yaml for apisix-ingress-controller deployment:
`apiVersion: apps/v1
kind: Deployment
metadata:
annotations:
deployment.kubernetes.io/revision: "2"
meta.helm.sh/release-name: apisix
meta.helm.sh/release-namespace: ingress-apisix
creationTimestamp: "2021-10-13T06:34:01Z"
generation: 2
labels:
app.kubernetes.io/instance: apisix
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: apisix-ingress-controller
app.kubernetes.io/version: 1.2.0
helm.sh/chart: apisix-ingress-controller-0.7.0
managedFields:
- apiVersion: apps/v1
manager: Go-http-client
operation: Update
time: "2021-10-13T06:34:01Z"
- apiVersion: apps/v1
manager: kube-controller-manager
operation: Update
time: "2021-10-13T06:34:56Z"
- apiVersion: apps/v1
manager: tke-apiserver
operation: Update
time: "2021-10-13T06:34:56Z"
name: apisix-apisix-ingress-controller
namespace: ingress-apisix
resourceVersion: "3084868080"
selfLink: /apis/apps/v1/namespaces/ingress-apisix/deployments/apisix-apisix-ingress-controller
uid: 14036a94-36d7-41d4-b1eb-9ac11efd495e
spec:
progressDeadlineSeconds: 600
replicas: 1
revisionHistoryLimit: 10
selector:
matchLabels:
app.kubernetes.io/instance: apisix
app.kubernetes.io/name: apisix-ingress-controller
strategy:
rollingUpdate:
maxSurge: 25%
maxUnavailable: 25%
type: RollingUpdate
template:
metadata:
annotations:
checksum/config: 7de7d76b8f372d076b361e308ae3cd400affb2e04ddddd059c9a86036bdbb9a9
qcloud-redeploy-timestamp: "1634106894913"
creationTimestamp: null
labels:
app.kubernetes.io/instance: apisix
app.kubernetes.io/name: apisix-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.2.0
imagePullPolicy: IfNotPresent
livenessProbe:
failureThreshold: 3
httpGet:
path: /healthz
port: 8080
scheme: HTTP
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
name: apisix-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
restartPolicy: Always
schedulerName: default-scheduler
securityContext: {}
serviceAccount: apisix-apisix-ingress-controller
serviceAccountName: apisix-apisix-ingress-controller
terminationGracePeriodSeconds: 30
volumes:
- configMap:
defaultMode: 420
items:
- key: config.yaml
path: config.yaml
name: apisix-configmap
name: configuration
status:
availableReplicas: 1
conditions:
- lastTransitionTime: "2021-10-13T06:34:11Z"
lastUpdateTime: "2021-10-13T06:34:11Z"
message: Deployment has minimum availability.
reason: MinimumReplicasAvailable
status: "True"
type: Available
- lastTransitionTime: "2021-10-13T06:34:01Z"
lastUpdateTime: "2021-10-13T06:34:56Z"
message: ReplicaSet "apisix-apisix-ingress-controller-7f9666dcc7" is progressing.
reason: ReplicaSetUpdated
status: "True"
type: Progressing
observedGeneration: 2
readyReplicas: 1
replicas: 2
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