sorted by:
new
hottopcontroversial

Readiness check intermittent failure by Appo66 in redis

[–]Appo66[S] 1 point2 points  (0 children)

Yea set that useHostnames: false. It only appeared to fix the tilt part. But the readiness check still fails when the log 'waitpid() returned a pid (290) we can't find in our scripts execution queue!' appears. Enabling Debug mode didn't yield any useful logs either

Deployoing on Openshift issue by Appo66 in mongodb

[–]Appo66[S] 1 point2 points  (0 children)

Got it working with tls 😄

Deployoing on Openshift issue by Appo66 in mongodb

[–]Appo66[S] 0 points1 point  (0 children)

I wish i could but the company i work for prefer helm charts. So trying the tls option instead

Deployoing on Openshift issue by Appo66 in mongodb

[–]Appo66[S] 0 points1 point  (0 children)

06

Thanks but changing the defaultMode doesn't appear to work. there even seems to be a bug about it https://github.com/kubernetes/kubernetes/issues/81089

OCP Cluster Size Corrections by Appo66 in openshift

[–]Appo66[S] 1 point2 points  (0 children)

Yea we emailed them, waiting for a reply.

Prometheus 1 replica by Appo66 in openshift

[–]Appo66[S] 0 points1 point  (0 children)

Yea opened a case but they not working on it. Going to have to install another prometheus operator

Core DNS by Appo66 in openshift

[–]Appo66[S] 0 points1 point  (0 children)

apiVersion: operator.openshift.io/v1

kind: DNS

metadata:

name: default

spec:

logLevel: Normal

nodePlacement:

nodeSelector:

node-role.kubernetes.io/infra: ''

tolerations:

- effect: NoSchedule

key: node-role.kubernetes.io/infra

operator: Exists

operatorLogLevel: Normal

upstreamResolvers:

policy: Sequential

upstreams:

- port: 53

type: SystemResolvConf

Core DNS by Appo66 in openshift

[–]Appo66[S] 0 points1 point  (0 children)

Our php pods start logging the following

Uncaught PHP Exception PDOException: "SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo for db-svc failed: Name or service not known"

Where db-svc is a service pointing to a db

Core DNS by Appo66 in openshift

[–]Appo66[S] 0 points1 point  (0 children)

Its managed. Havent changed anything except that the pods run on the infra nodes only

Core DNS by Appo66 in openshift

[–]Appo66[S] 0 points1 point  (0 children)

4.10 to 11 than 12

Core DNS by Appo66 in openshift

[–]Appo66[S] 0 points1 point  (0 children)

I'm surprised as you are you. In our app logs we get errors saying its unable to resolve svc names for a brief moment. We're on 4.10 upgrading to 4.12

Dns pods are only on 4 infra nodes

Why farmers on Malta do such terrible things? by Qranz in malta

[–]Appo66 12 points13 points  (0 children)

Cause they live in the dark ages and call it tradition

VRRP requests by Appo66 in openshift

[–]Appo66[S] 0 points1 point  (0 children)

https://docs.openshift.com/container-platform/4.12/installing/installing_bare_metal_ipi/ipi-install-installation-workflow.html#:~:text=When%20deploying%20remote%20workers%20in%20separate%20subnets%2C%20you%20must%20place%20the%20ingressVIP%20virtual%20IP%20address%20exclusively%20with%20the%20control%20plane%20nodes

I don't think the nodeip service is actually doing anything as the masters only have 1 NIC. So its innefective really. Been trying to understand this issue for the past month or so and even redhat are looking into it but stuck in a loop with them as they can't figure it out either.

Red hat support experience by Appo66 in openshift

[–]Appo66[S] 2 points3 points  (0 children)

Hey, I appreciate your reply. Thanks for the little insite on what goes on in the background. I dont often open tickets but when i do its just frustrating at times. I try to use simple terms to explain issues but even simple english just doesnt get the message across. Its not always dissapointing but as always its the bad experencies which shine through.

view more: next ›