Reza Farrahi M comments

Results 11 comments of


                                            Reza Farrahi M

EKS k8s 1.19 - AMI 1.19-v20210414 - (combined from similar events): System OOM encountered, victim process:

Please note that when at first we upgraded to k8s 1.19, we used the AMI version v20210329, and we had a lot of node NotReady issues. Based on this comment...

EKS k8s 1.19 - AMI 1.19-v20210414 - (combined from similar events): System OOM encountered, victim process:

Hi @roccozanni , any luck with `v20210519`? Thanks

EKS k8s 1.19 - AMI 1.19-v20210414 - (combined from similar events): System OOM encountered, victim process:

We have started the roll out to 1.19-v20211206 base on the suggestion from @mmerkes

predicate checking error: node(s) didn't match Pod's node affinity; predicateName=NodeAffinity; reasons: node(s) didn't match Pod's node affinity; debugInfo=

any update?

predicate checking error: node(s) didn't match Pod's node affinity; predicateName=NodeAffinity; reasons: node(s) didn't match Pod's node affinity; debugInfo=

/remove-lifecycle rotten

predicate checking error: node(s) didn't match Pod's node affinity; predicateName=NodeAffinity; reasons: node(s) didn't match Pod's node affinity; debugInfo=

/remove-lifecycle stale

Mysql dont start completely and readiness fail

I have a similar issue with the readiness probe. The workaround has been to delete the mysql-operator pod. Any advise? The mysql operator is on 0.3.8. Thanks

Mysql dont start completely and readiness fail

This could be a bug related to this delete table when it assumes the file does not exists while the file actually exists: https://github.com/bitpoke/mysql-operator/blob/18a6031621733203b43374b835eaa2fe59d35795/pkg/sidecar/appconf.go#L201-L205 I was able to make the...

Rancher reporting cpu/mem reserved and pod count wrong

remove-stale

Capability to ignore Resource Not Found errors in "az aks update-credentials"

As a workaround, the suggestion to disable monitoring add-on for the cluster helped: `az aks disable-addons -a monitoring --resource-group clusterresourcegroup --name clustername` (from here: https://github.com/Azure/AKS/issues/1380). However, still it would be...