Hi Team, I am Facing the following warning from the master pod when I deploy my Mendix application into private cloud. The build process was successfully completed by build pod and pushed to the ECR registry, After that the master pod is showing the following unhealthy warning, and the worker pod hasn’t started yet.. Unhealthy, Readiness probe failed: Get “http://192.168.186.**:8080/” : dial 192.168.186.**:8080: connect: connection refused. Note: I have attached the following screenshots below. Note: In the above Image you can see the build and runtime is showing success. operatorconfiguration file: # Please edit the object below. Lines beginning with a '#' will be ignored, # and an empty file will abort the edit. If an error occurs while saving this file will be # reopened with the relevant failures. # apiVersion: privatecloud.mendix.com/v1alpha1 kind: OperatorConfiguration metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"privatecloud.mendix.com/v1alpha1","kind":"OperatorConfiguration","metadata":{"annotations":{},"name":"mendix-operator-configuration","namespace":"latest"},"spec":{"buildResources":{"limits":{"cpu":"1","memory":"256Mi"},"requests":{"cpu":"250m","memory":"64Mi"}},"buildRuntimeBaseImage":"private-cloud.registry.mendix.com/runtime-base:{{.MxRuntimeVersion}}-rhel","endpoint":{"type":"ingress"},"metricsSidecarResources":{"limits":{"cpu":"100m","memory":"32Mi"},"requests":{"cpu":"100m","memory":"16Mi"}},"runtimeMetricsConfiguration":{"interval":"PT1M","mode":"native"},"runtimeResources":{"limits":{"cpu":"1000m","memory":"512Mi"},"requests":{"cpu":"100m","memory":"512Mi"}},"sidecarResources":{"limits":{"cpu":"1","memory":"2000Mi"},"requests":{"cpu":"100m","memory":"512Mi"}}}} creationTimestamp: "2022-04-21T05:18:52Z" generation: 5 name: mendix-operator-configuration namespace: latest resourceVersion: "8432635" uid: 88cbcf55-6bd4-4b3d-bc49-7152be1926e0 spec: buildResources: limits: cpu: "1" memory: 256Mi requests: cpu: 250m memory: 64Mi buildRuntimeBaseImage: private-cloud.registry.mendix.com/runtime-base:{{.MxRuntimeVersion}}-rhel endpoint: ingress: annotations: nginx.ingress.kubernetes.io/proxy-body-size: 500m domain: latest enableTLS: false path: / serviceAnnotations: service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: ip service.beta.kubernetes.io/aws-load-balancer-scheme: internet-facing service.beta.kubernetes.io/aws-load-balancer-type: external servicePorts: - 80 - 443 serviceType: LoadBalancer type: ingress metricsSidecarResources: limits: cpu: 100m memory: 32Mi requests: cpu: 100m memory: 16Mi registry: credentials: mendix-registry-ecr-secret imageNameTemplate: p7f7n4p0/mocecr:{{.Name}} pullURL: public.ecr.aws pushURL: public.ecr.aws type: ecr runtimeMetricsConfiguration: interval: PT1M mode: native runtimeResources: limits: cpu: 1000m memory: 512Mi requests: cpu: 100m memory: 512Mi sidecarResources: limits: cpu: 1 memory: 2000Mi requests: cpu: 100m memory: 512Mi Should I be adding something in the operatorconfiguration file. I request you to please provide me a solution for clearing the error.
asked
Roshan M
2 answers
0
Hello,
Has the root cause for this issue been identified? I’m having the same issue with AKS that I get the following warning messages every once in a few hours.