Skip to content

install can not ready #2860

@13567436138

Description

@13567436138

I have installed metrics server,but still can not ready

What happened:

I0526 06:49:09.102192  120964 main.go:333] "Starting profiling server" endpoint=":6062"
I0526 06:49:09.102238  120964 bpfrecorder.go:149] "Setting up caches with expiry of 1h0m0s" logger="bpf-recorder"
I0526 06:49:09.102284  120964 bpfrecorder.go:165] "Starting ebpf recorder on node: minio-01-d" logger="bpf-recorder"
I0526 06:49:09.103256  120964 bpfrecorder.go:196] "Connecting to metrics server" logger="bpf-recorder"
E0526 06:49:13.173781  120964 main.go:286] "running security-profiles-operator" err="connect to metrics server: connect to local GRPC server: wait on retry: timed out waiting for the condition" logger="setup"

What you expected to happen:

^Croot@minio-01-a:~# kubectl get pod -n spo -w
NAME                                                  READY   STATUS             RESTARTS      AGE
security-profiles-operator-5c6d69999c-4gg72           1/1     Running            0             2m48s
security-profiles-operator-5c6d69999c-gjvsr           1/1     Running            0             2m53s
security-profiles-operator-5c6d69999c-v9247           1/1     Running            0             2m51s
security-profiles-operator-webhook-56f85966fc-jdlzm   1/1     Running            0             73m
security-profiles-operator-webhook-56f85966fc-vbd6k   1/1     Running            0             73m
security-profiles-operator-webhook-56f85966fc-xlxfv   1/1     Running            0             73m
spod-4z25w                                            2/3     CrashLoopBackOff   8 (40s ago)   17m
spod-6rlwp                                            2/3     CrashLoopBackOff   8 (61s ago)   17m
spod-djrlr                                            2/3     CrashLoopBackOff   8 (47s ago)   17m
spod-sgh6z                                            2/3     CrashLoopBackOff   8 (64s ago)   17m
spod-tr82v                                            2/3     CrashLoopBackOff   8 (45s ago)

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Cloud provider or hardware configuration:
  • OS (e.g: cat /etc/os-release):
  • Kernel (e.g. uname -a):
  • Others:

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions