apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T06:34:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: 28c97880-3184-45ee-b876-b801ea4f0f00 resourceVersion: "54807" uid: e816ff84-f00d-478f-876a-0a6fddf9dc39 spec: sourcePod: network-check-source-989f8b8dc-wxf7f targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T06:41:41Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 848.026µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:09:41Z" - latency: 1.485397ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:08:41Z" - latency: 1.196476ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:07:41Z" - latency: 1.204724ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:06:41Z" - latency: 1.257809ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:05:41Z" - latency: 942.68µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:04:41Z" - latency: 1.262057ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:03:41Z" - latency: 823.487µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:02:41Z" - latency: 984.518µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:01:41Z" - latency: 1.053456ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:00:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T06:34:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: 28c97880-3184-45ee-b876-b801ea4f0f00 resourceVersion: "55936" uid: 1e92d4c7-28b7-490c-8306-9bb724a23dc6 spec: sourcePod: network-check-source-989f8b8dc-wxf7f targetEndpoint: a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T06:40:41Z" message: 'load-balancer-api-external: tcp connection to a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.785474ms message: 'load-balancer-api-external: tcp connection to a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:10:41Z" - latency: 7.091706ms message: 'load-balancer-api-external: resolved host name a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:10:41Z" - latency: 3.525779ms message: 'load-balancer-api-external: tcp connection to a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:09:41Z" - latency: 8.390313ms message: 'load-balancer-api-external: resolved host name a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:09:41Z" - latency: 4.622249ms message: 'load-balancer-api-external: tcp connection to a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:08:41Z" - latency: 7.316178ms message: 'load-balancer-api-external: resolved host name a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:08:41Z" - latency: 29.056172ms message: 'load-balancer-api-external: tcp connection to a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:07:41Z" - latency: 7.378932ms message: 'load-balancer-api-external: resolved host name a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:07:41Z" - latency: 5.98336ms message: 'load-balancer-api-external: tcp connection to a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:06:41Z" - latency: 8.059816ms message: 'load-balancer-api-external: resolved host name a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:06:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T06:34:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: 28c97880-3184-45ee-b876-b801ea4f0f00 resourceVersion: "55937" uid: b0a93f4d-9f30-403b-9b57-63927c7031f3 spec: sourcePod: network-check-source-989f8b8dc-wxf7f targetEndpoint: a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T06:40:41Z" message: 'load-balancer-api-internal: tcp connection to a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.844779ms message: 'load-balancer-api-internal: tcp connection to a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:10:41Z" - latency: 7.197253ms message: 'load-balancer-api-internal: resolved host name a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:10:41Z" - latency: 3.264587ms message: 'load-balancer-api-internal: tcp connection to a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:09:41Z" - latency: 8.240507ms message: 'load-balancer-api-internal: resolved host name a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:09:41Z" - latency: 6.399709ms message: 'load-balancer-api-internal: tcp connection to a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:08:41Z" - latency: 7.355687ms message: 'load-balancer-api-internal: resolved host name a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:08:41Z" - latency: 6.225992ms message: 'load-balancer-api-internal: tcp connection to a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:07:41Z" - latency: 7.4192ms message: 'load-balancer-api-internal: resolved host name a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:07:41Z" - latency: 5.347929ms message: 'load-balancer-api-internal: tcp connection to a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:06:41Z" - latency: 8.087633ms message: 'load-balancer-api-internal: resolved host name a027936688c8e467982d30f61726e24a-e9a32de15b6a022b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:06:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T06:34:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-network-check-target-ip-10-0-129-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: 28c97880-3184-45ee-b876-b801ea4f0f00 resourceVersion: "54805" uid: ad366e2e-9634-4ab5-a5a0-cbf0dc7c14c2 spec: sourcePod: network-check-source-989f8b8dc-wxf7f targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T06:41:41Z" message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 889.754µs message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:09:41Z" - latency: 1.222694ms message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:08:41Z" - latency: 1.496618ms message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:07:41Z" - latency: 1.410701ms message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:06:41Z" - latency: 1.070442ms message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:05:41Z" - latency: 1.332595ms message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:04:41Z" - latency: 830.421µs message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:03:41Z" - latency: 1.31872ms message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:02:41Z" - latency: 969.061µs message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:01:41Z" - latency: 853.813µs message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:00:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T06:34:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-network-check-target-ip-10-0-130-176 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: 28c97880-3184-45ee-b876-b801ea4f0f00 resourceVersion: "54806" uid: 69e54a9d-43c9-480c-925a-ff77e799b9dc spec: sourcePod: network-check-source-989f8b8dc-wxf7f targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T06:41:41Z" message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.193292ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:09:41Z" - latency: 2.200519ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:08:41Z" - latency: 2.169598ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:07:41Z" - latency: 2.580953ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:06:41Z" - latency: 2.455435ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:05:41Z" - latency: 2.317078ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:04:41Z" - latency: 2.07491ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:03:41Z" - latency: 2.233774ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:02:41Z" - latency: 1.977392ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:01:41Z" - latency: 2.207491ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:00:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T06:34:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-network-check-target-ip-10-0-133-92 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: 28c97880-3184-45ee-b876-b801ea4f0f00 resourceVersion: "54804" uid: fede6d2a-584b-4d93-92ce-f930a97f1432 spec: sourcePod: network-check-source-989f8b8dc-wxf7f targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T06:41:41Z" message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.833362ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:09:41Z" - latency: 1.996973ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:08:41Z" - latency: 1.732399ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:07:41Z" - latency: 2.016537ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:06:41Z" - latency: 1.906593ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:05:41Z" - latency: 1.702188ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:04:41Z" - latency: 1.848443ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:03:41Z" - latency: 1.688257ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:02:41Z" - latency: 1.985691ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:01:41Z" - latency: 1.581024ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:00:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T06:34:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: 28c97880-3184-45ee-b876-b801ea4f0f00 resourceVersion: "55935" uid: 0ed52cf4-0640-4833-b646-1edd48f66d91 spec: sourcePod: network-check-source-989f8b8dc-wxf7f targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T06:40:41Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.182794ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:10:41Z" - latency: 2.022293ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T07:10:41Z" - latency: 927.313µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:09:41Z" - latency: 1.918345ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T07:09:41Z" - latency: 1.002945ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:08:41Z" - latency: 2.458309ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T07:08:41Z" - latency: 886.824µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:07:41Z" - latency: 2.141656ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T07:07:41Z" - latency: 925.784µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:06:41Z" - latency: 2.537099ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T07:06:41Z" kind: List metadata: resourceVersion: ""