search

kubernetes-sigs / prow

Prow is a Kubernetes based CI/CD system developed to serve the Kubernetes community. This repository contains Prow source code and Hugo sources for Prow documentation site.
https://docs.prow.k8s.io
Apache License 2.0
127 stars 98 forks source link

Prow issue: I am installing containerd 1.7.16 and kubernetes 1.30.0 on RHEL centos machines onpremise.The pods are unable to run #187

Closed madhavikdb closed 5 months ago

madhavikdb commented 5 months ago

The pods are unable to run.Multiple issues are noticed.

apiserver, coredns, controller-manager, scheduler restarted 22 times Pod networking is failing(redis nodes unable to join,metrics server pods are working) containerd and kubelet status is showing error while fetching containerID Kubectl get events display "invalid 0 image filesystem capacity" Disk utiliation on one worker node goes to 84% always(with no pods) Expectations:

Perfectly working cluster with. image and node filesystem to automatically garbage collect with default configurations Able to use runc container runtime and schedule pods pod networking use private registry and local images INSTALLATION PROCEDURE:

Downloaded RPM'S

Skipped rpms(glibc, iptable,iproute,systemd,system-libs,utils-linux ) as Faced conflicts while installing rpms as slightly lower versions are already present in system.

1.7.16 containerd,1.4.1 CNI plugin without package manager, Containerd , stage directory (/data/containers and /data/containerd) Consumption is going to 84 percent with no pods running(state directory not GC automatically)

installed cluster using kubeadm

CNI flannel Deployed

matthyx commented 5 months ago

hi @madhavikdb how is this related to prow? It seems your cluster isn't properly running before you start installing it.

madhavikdb commented 5 months ago

Cluster

hi @madhavikdb how is this related to prow? It seems your cluster isn't properly running before you start installing it.

Cluster Component status show ok Restarts are found in api-server,etcd,controllermanger-scheduler kubelet logs show "failed retieving ContainerID"

Can you help me where the cluster setup went wrong, its working with systems with internet connection.It is failing with system without internet connection.

neolit123 commented 5 months ago

a better place to ask would be on the support channels. please see: https://git.k8s.io/kubernetes/SUPPORT.md

/kind support /close

k8s-ci-robot commented 5 months ago

@neolit123: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/prow/issues/187#issuecomment-2177903239): >a better place to ask would be on the support channels. please see: >https://git.k8s.io/kubernetes/SUPPORT.md > >/kind support >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.