-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HCP api pod at 20 cores #175
Comments
Its not really getting better, now we have two kube-apiserver pods >20 cores. May I kill one of those and see what happens? @rbo , wdyt? |
|
Try to fix it very quick:
|
Nothing changed.. |
When you identified the root cause: I think it would also be good to have
some limits in place, to prevent this from consuming so many resources.
…On Mon, Jun 10, 2024 at 1:35 PM Robert Bohne ***@***.***> wrote:
oc adm top pod --sum --sort-by=cpu -n rbohne-hcp-sendling
NAME CPU(cores) MEMORY(bytes)
kube-apiserver-86548cbbbf-r6grl 18262m 2289Mi
kube-apiserver-86548cbbbf-btmct 15798m 2114Mi
virt-launcher-sendling-ff7bf3fd-pn5vs-q8w7v 6153m 16178Mi
kube-apiserver-86548cbbbf-bhsfj 5517m 4611Mi
etcd-0 2303m 616Mi
openshift-apiserver-778f9db75c-6pjb5 1254m 333Mi
etcd-1 1109m 861Mi
ignition-server-5b4567866-kl4xf 1064m 414Mi
ignition-server-5b4567866-w568x 1017m 333Mi
ignition-server-5b4567866-b7ksx 990m 372Mi
olm-operator-54d975b8c4-xtlmk 800m 404Mi
hosted-cluster-config-operator-748dbf6695-6kng2 537m 151Mi
etcd-2 338m 536Mi
konnectivity-agent-8599fd5d6b-sr6pn 272m 45Mi
openshift-apiserver-778f9db75c-kc7m9 241m 272Mi
konnectivity-agent-8599fd5d6b-f8nkz 199m 29Mi
openshift-oauth-apiserver-584f69b7f9-f4jmm 182m 117Mi
openshift-oauth-apiserver-584f69b7f9-9qd99 167m 96Mi
kube-controller-manager-5fc9d96bdf-d2mgv 153m 300Mi
packageserver-7f976d7855-brh6g 89m 289Mi
packageserver-7f976d7855-bp87j 79m 259Mi
openshift-oauth-apiserver-584f69b7f9-7c2mp 69m 82Mi
control-plane-operator-646886cd59-knl2g 50m 338Mi
redhat-operators-catalog-5778b9f69d-9ppd4 21m 84Mi
certified-operators-catalog-5f585b98cd-5xz5z 17m 133Mi
redhat-marketplace-catalog-867f99df5-grcnn 16m 68Mi
openshift-apiserver-778f9db75c-zjqcj 16m 325Mi
community-operators-catalog-79c49fb477-krzt8 15m 143Mi
openshift-route-controller-manager-869c7c988b-xrncf 15m 60Mi
packageserver-7f976d7855-tv5pb 14m 258Mi
virt-launcher-sendling-10d195e8-j8czd-sjshq 13m 1495Mi
cluster-network-operator-9664cbc94-mcmng 10m 286Mi
machine-approver-85cb867c5-hdr2z 10m 99Mi
cluster-policy-controller-74964cb9d6-6svtg 8m 192Mi
openshift-controller-manager-5578f894bb-4c9vn 6m 60Mi
openshift-controller-manager-5578f894bb-7dd7p 6m 175Mi
kube-controller-manager-5fc9d96bdf-7wjrs 5m 60Mi
kube-scheduler-5b5c9478f4-7rdng 5m 51Mi
capi-provider-7f58f475dd-h68hg 4m 70Mi
cluster-storage-operator-7fcdf884fb-8t2mf 4m 81Mi
openshift-route-controller-manager-869c7c988b-8rjtd 4m 76Mi
cluster-api-c7b575bb4-zg64v 3m 101Mi
ovnkube-control-plane-75bffb695c-dq6fc 3m 143Mi
ignition-server-proxy-57c4f77c97-6qn9r 2m 115Mi
csi-snapshot-controller-operator-797bf595d9-n5csv 2m 81Mi
multus-admission-controller-568bb6cd65-8wr2v 2m 93Mi
catalog-operator-74c748d567-2h9h8 2m 313Mi
kube-controller-manager-5fc9d96bdf-5x4lp 2m 60Mi
openshift-route-controller-manager-869c7c988b-kp2kh 2m 78Mi
kube-scheduler-5b5c9478f4-kpq4l 2m 93Mi
oauth-openshift-6b8fc486c9-gl7s4 2m 106Mi
oauth-openshift-6b8fc486c9-q8d5m 2m 82Mi
ingress-operator-7878df55d7-mq7cm 2m 193Mi
cluster-autoscaler-679d6fbdf6-p87xg 1m 120Mi
ignition-server-proxy-57c4f77c97-8n7f5 1m 135Mi
cluster-image-registry-operator-69754bbcc9-kchgs 1m 141Mi
cluster-policy-controller-74964cb9d6-v2jnb 1m 37Mi
openshift-controller-manager-5578f894bb-6rkvb 1m 62Mi
kube-scheduler-5b5c9478f4-98vnz 1m 63Mi
ignition-server-proxy-57c4f77c97-frg8q 1m 107Mi
oauth-openshift-6b8fc486c9-bgkpf 1m 79Mi
kubevirt-cloud-controller-manager-974969547-9kq6w 1m 67Mi
csi-snapshot-webhook-7c66684757-br56b 0m 36Mi
cluster-version-operator-55f8dfbdd7-k2g4c 0m 169Mi
csi-snapshot-controller-7cdd696bfd-hczrf 0m 35Mi
ovnkube-control-plane-75bffb695c-bgm4m 0m 112Mi
ovnkube-control-plane-75bffb695c-bxpzh 0m 106Mi
konnectivity-agent-8599fd5d6b-2brl7 0m 34Mi
dns-operator-5d6f5c64b9-2w8hn 0m 53Mi
cluster-policy-controller-74964cb9d6-6pqmj 0m 35Mi
cluster-node-tuning-operator-58764957cb-bhjwc 0m 73Mi
kubevirt-csi-controller-54d7884b4b-r8rtj 0m 142Mi
network-node-identity-8495fd79d9-zw2r5 0m 160Mi
network-node-identity-8495fd79d9-sxnw9 0m 98Mi
network-node-identity-8495fd79d9-sqkbl 0m 102Mi
________ ________
56867m 38218Mi
Nothing changed..
—
Reply to this email directly, view it on GitHub
<#175 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AENMQWZXGENQ7VBZQKQLVMLZGWFODAVCNFSM6AAAAABILWIEN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJYGEYDEMBZG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Daniel Fröhlich (He/Him/His) - Principal Product Manager OpenShift Edge
Red Hat GmbH - Registered seat: Werner von Siemens Ring 12, D-85630
Grasbrunn, Germany - Commercial register: Amtsgericht Muenchen/Munich, HRB
153243 - Managing Directors: Ryan Barnhart, Charles Cachera, Michael
O'Neill, Amy Ross
|
@DanielFroehlich Agree! Looks like a upgrade is running: |
Red Hat SSO config is broken on that cluster. Let's fix this first. |
Try to fetch from the pod where the VM is running:
|
The other vm pod can not curl as well.. |
Sorry noo time anymore and sendling is not importend. Deleted. Problem solved :-/ |
Documented at the wrong issue: Try the curl from another pod on the same node:
=> works, Unauthorized is expected. Resolve conf is the same.
|
While playing with acm observability, I realised we have two HCP cluster where an API server pod is consuming >20cores.
![image](https://private-user-images.githubusercontent.com/18532443/334203671-8dc09c17-a2ec-4976-82c0-36740cf583fc.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjMwOTI0MTcsIm5iZiI6MTcyMzA5MjExNywicGF0aCI6Ii8xODUzMjQ0My8zMzQyMDM2NzEtOGRjMDljMTctYTJlYy00OTc2LTgyYzAtMzY3NDBjZjU4M2ZjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MDglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODA4VDA0NDE1N1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWRhMjI2NDI0NjJmMjI5NmJjNzBmMDE1NTZlMmViMDlmZDdjM2VmYjM4MzU1NjliODgzN2ZhYjI1NTVlOWFlM2ImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.R-HnW8MIVo29kGAi8WPZvBpSnRqNQWoUrlL24wleViA)
That does not feel right!
See e.g. here:
From: https://console-openshift-console.apps.isar.coe.muc.redhat.com/k8s/ns/rbohne-hcp-sendling/replicasets/kube-apiserver-86548cbbbf/pods
Same for rbohne-hcp-sendling-ingress
The text was updated successfully, but these errors were encountered: