apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T09:15:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-161-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-161.ec2.internal uid: 95f55dea-23f8-421f-9ae7-aca109c150ca resourceVersion: "22042" uid: 01312eb2-97ca-4118-9df1-760fd21db93a spec: sourcePod: network-check-source-6f8b768455-dvwnf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-11T09:23:00Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 901.503µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:44:00Z" - latency: 1.005463ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:43:00Z" - latency: 969.611µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:42:00Z" - latency: 1.119217ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:41:00Z" - latency: 852.43µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:40:00Z" - latency: 922.541µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:39:00Z" - latency: 1.54751ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:38:00Z" - latency: 1.326581ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:37:00Z" - latency: 1.011837ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:36:00Z" - latency: 1.795408ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:35:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T09:15:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-161-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-161.ec2.internal uid: 95f55dea-23f8-421f-9ae7-aca109c150ca resourceVersion: "20293" uid: e4e4d1ce-35cf-431b-a0cc-51d9e0ef6e41 spec: sourcePod: network-check-source-6f8b768455-dvwnf targetEndpoint: a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T09:22:00Z" message: 'load-balancer-api-external: tcp connection to a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.415738ms message: 'load-balancer-api-external: tcp connection to a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:40:00Z" - latency: 8.841093ms message: 'load-balancer-api-external: resolved host name a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T09:40:00Z" - latency: 8.288458ms message: 'load-balancer-api-external: tcp connection to a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:39:00Z" - latency: 8.545502ms message: 'load-balancer-api-external: resolved host name a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T09:39:00Z" - latency: 4.686575ms message: 'load-balancer-api-external: tcp connection to a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:38:00Z" - latency: 9.1308ms message: 'load-balancer-api-external: resolved host name a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T09:38:00Z" - latency: 6.538435ms message: 'load-balancer-api-external: tcp connection to a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:37:00Z" - latency: 10.994203ms message: 'load-balancer-api-external: resolved host name a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T09:37:00Z" - latency: 6.369513ms message: 'load-balancer-api-external: tcp connection to a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:36:00Z" - latency: 8.536251ms message: 'load-balancer-api-external: resolved host name a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T09:36:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T09:15:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-161-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-161.ec2.internal uid: 95f55dea-23f8-421f-9ae7-aca109c150ca resourceVersion: "20294" uid: f3dac886-3f14-44bf-9bc3-7d96cd58603d spec: sourcePod: network-check-source-6f8b768455-dvwnf targetEndpoint: a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T09:22:00Z" message: 'load-balancer-api-internal: tcp connection to a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.398788ms message: 'load-balancer-api-internal: tcp connection to a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:40:00Z" - latency: 8.816292ms message: 'load-balancer-api-internal: resolved host name a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T09:40:00Z" - latency: 4.904347ms message: 'load-balancer-api-internal: tcp connection to a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:39:00Z" - latency: 8.566039ms message: 'load-balancer-api-internal: resolved host name a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T09:39:00Z" - latency: 4.667334ms message: 'load-balancer-api-internal: tcp connection to a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:38:00Z" - latency: 9.097063ms message: 'load-balancer-api-internal: resolved host name a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T09:38:00Z" - latency: 5.534951ms message: 'load-balancer-api-internal: tcp connection to a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:37:00Z" - latency: 10.969075ms message: 'load-balancer-api-internal: resolved host name a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T09:37:00Z" - latency: 5.105639ms message: 'load-balancer-api-internal: tcp connection to a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:36:00Z" - latency: 8.439335ms message: 'load-balancer-api-internal: resolved host name a6f9d521316744a22a9386b2030b4b8a-e57533f9fed84473.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T09:36:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T09:15:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-161-to-network-check-target-ip-10-0-135-119 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-161.ec2.internal uid: 95f55dea-23f8-421f-9ae7-aca109c150ca resourceVersion: "22040" uid: 3c48a135-e02b-4066-a80b-7a1b76241923 spec: sourcePod: network-check-source-6f8b768455-dvwnf targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-11T09:23:00Z" message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.958569ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:44:00Z" - latency: 1.832051ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:43:00Z" - latency: 1.980508ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:42:00Z" - latency: 1.888024ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:41:00Z" - latency: 1.848049ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:40:00Z" - latency: 1.819354ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:39:00Z" - latency: 1.691015ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:38:00Z" - latency: 1.682171ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:37:00Z" - latency: 1.918993ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:36:00Z" - latency: 2.066219ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:35:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T09:15:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-161-to-network-check-target-ip-10-0-137-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-161.ec2.internal uid: 95f55dea-23f8-421f-9ae7-aca109c150ca resourceVersion: "22039" uid: cfff34d5-5b94-4810-8456-aa9031bf6101 spec: sourcePod: network-check-source-6f8b768455-dvwnf targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-11T09:23:00Z" message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 942.16µs message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:44:00Z" - latency: 1.194323ms message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:43:00Z" - latency: 887.438µs message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:42:00Z" - latency: 1.006527ms message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:41:00Z" - latency: 799.505µs message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:40:00Z" - latency: 1.645211ms message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:39:00Z" - latency: 755.62µs message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:38:00Z" - latency: 882.925µs message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:37:00Z" - latency: 889.451µs message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:36:00Z" - latency: 1.165472ms message: 'network-check-target-ip-10-0-137-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:35:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T09:15:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-161-to-network-check-target-ip-10-0-143-146 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-161.ec2.internal uid: 95f55dea-23f8-421f-9ae7-aca109c150ca resourceVersion: "22041" uid: 16e9955d-22c2-475f-bd04-872f332c224a spec: sourcePod: network-check-source-6f8b768455-dvwnf targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-11T09:23:00Z" message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.105047ms message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:44:00Z" - latency: 2.224742ms message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:43:00Z" - latency: 1.898163ms message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:42:00Z" - latency: 1.859349ms message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:41:00Z" - latency: 2.210932ms message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:40:00Z" - latency: 2.234735ms message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:39:00Z" - latency: 2.048016ms message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:38:00Z" - latency: 2.225726ms message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:37:00Z" - latency: 2.316311ms message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:36:00Z" - latency: 3.041676ms message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:35:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T09:15:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-161-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-161.ec2.internal uid: 95f55dea-23f8-421f-9ae7-aca109c150ca resourceVersion: "20292" uid: c38fc9a2-4e05-40cc-ada9-d31c4b64207b spec: sourcePod: network-check-source-6f8b768455-dvwnf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-11T09:22:00Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 820.06µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:40:00Z" - latency: 1.714398ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T09:40:00Z" - latency: 735.91µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:39:00Z" - latency: 1.851ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T09:39:00Z" - latency: 741.316µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:38:00Z" - latency: 2.704284ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T09:38:00Z" - latency: 796.904µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:37:00Z" - latency: 1.89735ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T09:37:00Z" - latency: 848.112µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T09:36:00Z" - latency: 2.070329ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T09:36:00Z" kind: List metadata: resourceVersion: ""