-
|
Hello, Only when the IssueWhile the TS progressing 90-10… until 100 no requests are served by the canary service when I try the ingress endpoint. Here are some
rollout.yamlapiVersion: argoproj.io/v1alpha1
kind: Rollout
metadata:
name: {{ include "infoevent.fullname" . }}
labels:
app: {{ .Release.Name }}
version: {{ .Chart.AppVersion }}
spec:
strategy:
canary:
# Reference to a Service which the controller will update to point to the canary ReplicaSet
canaryService: "rollout-{{ .Release.Name }}-canary"
# Reference to a Service which the controller will update to point to the stable ReplicaSet
stableService: "rollout-{{ .Release.Name }}-stable"
trafficRouting:
smi: {}
steps:
- setWeight: 10
- pause: {duration: 2m}
- setWeight: 25
- pause: {duration: 2m}
- setWeight: 50
- pause: {duration: 2m}
- setWeight: 75
revisionHistoryLimit: 2
selector:
matchLabels:
{{- include "infoevent.selectorLabels" . | nindent 6 }}
app: {{ .Release.Name }}
template:
metadata:
{{- with .Values.podAnnotations }}
annotations:
{{- toYaml . | nindent 8 }}
{{- end }}
labels:
{{- include "infoevent.selectorLabels" . | nindent 8 }}
app: {{ .Release.Name }}
version: {{ .Chart.AppVersion }}
spec:
{{- with .Values.imagePullSecrets }}
imagePullSecrets:
{{- toYaml . | nindent 8 }}
{{- end }}
serviceAccountName: {{ include "infoevent.serviceAccountName" . }}
securityContext:
{{- toYaml .Values.podSecurityContext | nindent 8 }}
{{ if eq .Values.dc "amazon_va" }}
nodeSelector:
instance: "{{ .Values.nodeSelector.instance }}"
tolerations:
- key: "{{ .Values.tolerations.key }}"
operator: "{{ .Values.tolerations.operator }}"
effect: "{{ .Values.tolerations.effect }}"
{{ end }}
containers:
- env:
- name: DC_NAME
value: "{{ .Values.dc }}"
- name: DC
value: "{{ .Values.dc }}"
- name: APPD_TIER
value: "{{ .Values.appd_tier }}"
- name: APPD_OPTS
value: "{{ .Values.java_options }}"
- name: APPD_APP_NAME
value: "{{ .Values.appd_app_name }}"
- name: JMX_REMOTE_PORT
value: "{{ .Values.jmx_remote_port }}"
- name: IMAGE_TAG
value: "{{ .Values.image.tag }}"
image: "{{ .Values.image.repository }}:{{ .Values.image.tag | default .Chart.AppVersion }}"
imagePullPolicy: {{ .Values.image.pullPolicy }}
livenessProbe:
failureThreshold: 2
httpGet:
path: "/{{ .Release.Name }}/checkinit/final"
port: 8402
scheme: HTTP
initialDelaySeconds: 150
periodSeconds: 5
successThreshold: 1
timeoutSeconds: 2
name: infoevent
ports:
- containerPort: 8402
name: http
protocol: TCP
readinessProbe:
failureThreshold: 30
httpGet:
path: "/{{ .Release.Name }}/checkinit/final"
port: 8402
scheme: HTTP
initialDelaySeconds: 10
periodSeconds: 5
successThreshold: 1
timeoutSeconds: 1
resources:
limits:
cpu: "{{ .Values.resources.limits.cpu }}"
memory: "{{ .Values.resources.limits.memory }}"
requests:
cpu: "{{ .Values.resources.requests.cpu }}"
memory: "{{ .Values.resources.requests.memory }}"
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
- mountPath: /AppAgent.4.3.0.2
name: shared-data
dnsPolicy: ClusterFirst
dnsConfig:
searches:
- my-domain.com
initContainers:
- args:
- cp -r /AppAgent.4.3.0.2/* /appd/
command:
- /bin/sh
- -c
image: registry.my-registry/adplatform/appdynamics/rtb:4.3.0.2-v0.2.3
imagePullPolicy: {{ .Values.image.pullPolicy }}
name: appdagent
resources: {}
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
- mountPath: /appd
name: shared-data
restartPolicy: Always
schedulerName: default-scheduler
serviceAccount: rtbmicroservice-infoevent
terminationGracePeriodSeconds: 30
volumes:
- emptyDir: {}
name: shared-dataIngress.yamlapiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: "rollouts-{{ .Release.Name }}-stable"
namespace: production
labels:
app: {{ .Release.Name }}
annotations:
kubernetes.io/ingress.class: "nginx"
nginx.ingress.kubernetes.io/configuration-snippet: |
proxy_set_header l5d-dst-override $service_name.$namespace.svc.cluster.local:$service_port;
# proxy_hide_header l5d-remote-ip;
# proxy_hide_header l5d-server-id;
spec:
rules:
- host: {{ .Release.Name }}.my-domain.com
http:
paths:
# - path: "/infoevent"
- backend:
serviceName: "rollout-{{ .Release.Name }}-stable"
servicePort: 8402services.yamlapiVersion: v1
kind: Service
metadata:
name: rollout-{{ .Release.Name }}-canary
spec:
ports:
- port: 8402
targetPort: http
protocol: TCP
name: http
selector:
app: {{ .Release.Name }}
# This selector will be updated with the pod-template-hash of the canary ReplicaSet. e.g.:
# rollouts-pod-template-hash: 7bf84f9696
---
apiVersion: v1
kind: Service
metadata:
name: rollout-{{ .Release.Name }}-stable
spec:
ports:
- port: 8402
targetPort: http
protocol: TCP
name: http
selector:
app: {{ .Release.Name }}
# This selector will be updated with the pod-template-hash of the stable ReplicaSet. e.g.:
# rollouts-pod-template-hash: 789746c88dvalues.yaml# Default values for prd.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
# replicaCount: 2
image:
repository: "registry.my-domain
<img width="2557" alt="Screen Shot 2021-05-04 at 11 30 37" src="https://user-images.githubusercontent.com/4179195/116978304-33f60880-accc-11eb-943b-4416e31246ed.png">
.com/adplatform/infoevent"
pullPolicy: IfNotPresent
# Overrides the image tag whose default is the chart appVersion.
tag: v0.1.53
version: ""
imagePullSecrets: [
name: regcred
]
nameOverride: ""
fullnameOverride: ""
serviceAccount:
# Specifies whether a service account should be created
create: true
# Annotations to add to the service account
annotations: {}
# The name of the service account to use.
# If not set and create is true, a name is generated using the fullname template
name: ""
podAnnotations:
linkerd.io/inject: enabled
config.linkerd.io/proxy-cpu-limit: "1"
config.linkerd.io/proxy-cpu-request: "0.2"
config.linkerd.io/proxy-memory-limit: 2Gi
config.linkerd.io/proxy-memory-request: 128Mi
podSecurityContext: {}
# fsGroup: 2000
securityContext:
capabilities:
drop:
- ALL
readOnlyRootFilesystem: true
runAsNonRoot: true
runAsUser: 1001
service:
type: ClusterIP
port: None
targetPort: None
ingress:
enabled: true
resources:
limits:
cpu: "4000m"
memory: "8192Mi"
requests:
cpu: "2000m"
memory: "4096Mi"
autoscaling:
enabled: true
minReplicas: 3
maxReplicas: 5
targetCPUUtilizationPercentage: 65
# targetMemoryUtilizationPercentage: 90
tolerations: []
affinity: {}
port: "8402"
public: "true"
dc: "" |
Beta Was this translation helpful? Give feedback.
Answered by
haim-ari
May 4, 2021
Replies: 3 comments
-
UpdateI noticed there is something wrong with kubectl get pods -n ingress-nginx
NAME READY STATUS RESTARTS AGE
flagger-674b58f457-94vj4 1/1 Running 0 6d19h
flagger-prometheus-596d6965cb-xpf2f 1/1 Running 0 6d19h
ingress-nginx-admission-patch-knwsb 1/2 NotReady 1 2m36s
ingress-nginx-controller-5j2mt 1/1 Running 0 4m19s
ingress-nginx-controller-gcx6j 1/1 Running 0 3m56s
ingress-nginx-controller-wgccs 1/1 Running 0 3m22sI tried to remove the ingress apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
name: ingress-nginx
namespace: ingress-nginx
annotations:
fluxcd.io/ignore: "false"
spec:
interval: 5m
chart:
spec:
chart: ingress-nginx
version: '3.12.0'
sourceRef:
kind: HelmRepository
name: ingress-nginx
namespace: flux-system
interval: 1m
values:
controller:
metrics:
enabled: "true"
podAnnotations:
# linkerd.io/inject: ingress
prometheus.io/scrape: "true"
prometheus.io/port: "10254"
hostNetwork: "true"
kind: DaemonSet
service:
type: NodePortWhen adding the PodAnnotation for the ingress, This is how it looks:When I re-added the annotation it seems to be set on the ingress pods, but still traffic is not shifting correctly
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Seems that the issue is related to this: kubectl -n ingress-nginx get ds/ingress-nginx-controller -o yaml | linkerd inject - | kubectl apply -f -This is the ingress config: (this is RKE cluster which runs on bare metal) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Fixed the issue by:
After re-deploying the daemonSet, the ingress pods have the correct annotations and Environment Variables of Lnkerd: And I can see that the ingress is now Most important i'm now getting the canary app version when testing during canary release, according to the progress of the weight. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
haim-ari
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Fixed the issue by:
ingress-nginxnamespace (caused the patching issue of the ingress controller)controller.Service.Type: ""After re-deploying the daemonSet, the ingress pods have the correct annotations and Environment Variables of Lnkerd: