apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:14:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-28-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-28.ec2.internal uid: d9edfd45-f592-49f5-b08f-3a80c3dcd4b3 resourceVersion: "54290" uid: 615e7543-6c95-4b54-924a-256a7b8cbdbc spec: sourcePod: network-check-source-989f8b8dc-jtpjz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T23:21:03Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 874.212µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:49:03Z" - latency: 905.887µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:48:03Z" - latency: 1.207336ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:47:03Z" - latency: 1.314612ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:46:03Z" - latency: 957.853µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:45:03Z" - latency: 1.057217ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:44:03Z" - latency: 1.104314ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:43:03Z" - latency: 1.228788ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:42:03Z" - latency: 1.208471ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:41:03Z" - latency: 1.140084ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:40:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:14:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-28-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-28.ec2.internal uid: d9edfd45-f592-49f5-b08f-3a80c3dcd4b3 resourceVersion: "55229" uid: 1daa5837-9a1a-4ff9-9ae5-021abfbff70a spec: sourcePod: network-check-source-989f8b8dc-jtpjz targetEndpoint: a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T23:20:03Z" message: 'load-balancer-api-external: tcp connection to a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.578779ms message: 'load-balancer-api-external: tcp connection to a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:50:03Z" - latency: 7.648895ms message: 'load-balancer-api-external: resolved host name a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:50:03Z" - latency: 4.409251ms message: 'load-balancer-api-external: tcp connection to a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:49:03Z" - latency: 7.515903ms message: 'load-balancer-api-external: resolved host name a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:49:03Z" - latency: 5.950073ms message: 'load-balancer-api-external: tcp connection to a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:48:03Z" - latency: 7.664662ms message: 'load-balancer-api-external: resolved host name a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:48:03Z" - latency: 4.348579ms message: 'load-balancer-api-external: tcp connection to a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:47:03Z" - latency: 6.353269ms message: 'load-balancer-api-external: resolved host name a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:47:03Z" - latency: 5.173539ms message: 'load-balancer-api-external: tcp connection to a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:46:03Z" - latency: 7.933214ms message: 'load-balancer-api-external: resolved host name a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:46:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:14:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-28-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-28.ec2.internal uid: d9edfd45-f592-49f5-b08f-3a80c3dcd4b3 resourceVersion: "55228" uid: 06d563fe-d5bc-4f78-923b-b42873f31e45 spec: sourcePod: network-check-source-989f8b8dc-jtpjz targetEndpoint: a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T23:20:03Z" message: 'load-balancer-api-internal: tcp connection to a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.607325ms message: 'load-balancer-api-internal: tcp connection to a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:50:03Z" - latency: 7.711971ms message: 'load-balancer-api-internal: resolved host name a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:50:03Z" - latency: 4.368535ms message: 'load-balancer-api-internal: tcp connection to a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:49:03Z" - latency: 7.561107ms message: 'load-balancer-api-internal: resolved host name a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:49:03Z" - latency: 5.966087ms message: 'load-balancer-api-internal: tcp connection to a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:48:03Z" - latency: 7.78133ms message: 'load-balancer-api-internal: resolved host name a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:48:03Z" - latency: 4.301881ms message: 'load-balancer-api-internal: tcp connection to a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:47:03Z" - latency: 6.380779ms message: 'load-balancer-api-internal: resolved host name a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:47:03Z" - latency: 4.922849ms message: 'load-balancer-api-internal: tcp connection to a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:46:03Z" - latency: 7.869706ms message: 'load-balancer-api-internal: resolved host name a49d69362784547be81a2b14b16aa655-13f01d68398eb4c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:46:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:14:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-28-to-network-check-target-ip-10-0-132-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-28.ec2.internal uid: d9edfd45-f592-49f5-b08f-3a80c3dcd4b3 resourceVersion: "54288" uid: 3a1eb57e-0021-4013-83b2-1e8eadf4432b spec: sourcePod: network-check-source-989f8b8dc-jtpjz targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T23:21:03Z" message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.072079ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:49:03Z" - latency: 1.775622ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:48:03Z" - latency: 2.22785ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:47:03Z" - latency: 1.844979ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:46:03Z" - latency: 2.086331ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:45:03Z" - latency: 2.272425ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:44:03Z" - latency: 1.841026ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:43:03Z" - latency: 1.757034ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:42:03Z" - latency: 2.024156ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:41:03Z" - latency: 1.662368ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:40:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:14:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-28-to-network-check-target-ip-10-0-134-28 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-28.ec2.internal uid: d9edfd45-f592-49f5-b08f-3a80c3dcd4b3 resourceVersion: "54287" uid: 8ea3f789-daae-40fa-85e8-07e41addf1d7 spec: sourcePod: network-check-source-989f8b8dc-jtpjz targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T23:21:03Z" message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.110496ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:49:03Z" - latency: 1.031954ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:48:03Z" - latency: 908.563µs message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:47:03Z" - latency: 948.578µs message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:46:03Z" - latency: 789.946µs message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:45:03Z" - latency: 1.399645ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:44:03Z" - latency: 856.462µs message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:43:03Z" - latency: 996.851µs message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:42:03Z" - latency: 1.373508ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:41:03Z" - latency: 840.51µs message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:40:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:14:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-28-to-network-check-target-ip-10-0-140-52 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-28.ec2.internal uid: d9edfd45-f592-49f5-b08f-3a80c3dcd4b3 resourceVersion: "54289" uid: e9cb25ae-c327-48ec-af16-37f4d7d68e07 spec: sourcePod: network-check-source-989f8b8dc-jtpjz targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T23:21:03Z" message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.394316ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:49:03Z" - latency: 2.212261ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:48:03Z" - latency: 2.323212ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:47:03Z" - latency: 1.948441ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:46:03Z" - latency: 1.888592ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:45:03Z" - latency: 2.238135ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:44:03Z" - latency: 2.06522ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:43:03Z" - latency: 2.311528ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:42:03Z" - latency: 2.357783ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:41:03Z" - latency: 2.199499ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:40:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:14:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-28-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-28.ec2.internal uid: d9edfd45-f592-49f5-b08f-3a80c3dcd4b3 resourceVersion: "55227" uid: da657a22-4859-4985-905e-e3897ea22c06 spec: sourcePod: network-check-source-989f8b8dc-jtpjz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T23:20:03Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 801.506µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:50:03Z" - latency: 1.794165ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T23:50:03Z" - latency: 1.061814ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:49:03Z" - latency: 1.879758ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T23:49:03Z" - latency: 988.222µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:48:03Z" - latency: 1.987854ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T23:48:03Z" - latency: 812.716µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:47:03Z" - latency: 1.649106ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T23:47:03Z" - latency: 855.35µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:46:03Z" - latency: 2.000252ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T23:46:03Z" kind: List metadata: resourceVersion: ""