apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:14:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-204-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-204.ec2.internal uid: 54b78873-9f5a-4785-949d-d3272ad12384 resourceVersion: "25684" uid: ce269ce3-ff7f-4972-86b9-7639eb061a82 spec: sourcePod: network-check-source-7d88cb55d8-b9t7f targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T17:21:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 891.932µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:42:51Z" - latency: 1.059072ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:41:51Z" - latency: 809.939µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:40:51Z" - latency: 1.009432ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:39:51Z" - latency: 1.059409ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:38:51Z" - latency: 972.22µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:37:51Z" - latency: 1.446362ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:36:51Z" - latency: 829.588µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:35:51Z" - latency: 975.38µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:34:51Z" - latency: 1.111071ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:33:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:14:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-204-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-204.ec2.internal uid: 54b78873-9f5a-4785-949d-d3272ad12384 resourceVersion: "26776" uid: bef91827-da85-41d1-86eb-7d9f520a5dc3 spec: sourcePod: network-check-source-7d88cb55d8-b9t7f targetEndpoint: ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T17:20:51Z" message: 'load-balancer-api-external: tcp connection to ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.248507ms message: 'load-balancer-api-external: tcp connection to ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:44:51Z" - latency: 7.235903ms message: 'load-balancer-api-external: resolved host name ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:44:51Z" - latency: 4.544839ms message: 'load-balancer-api-external: tcp connection to ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:43:51Z" - latency: 6.543887ms message: 'load-balancer-api-external: resolved host name ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:43:51Z" - latency: 4.011061ms message: 'load-balancer-api-external: tcp connection to ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:42:51Z" - latency: 7.64898ms message: 'load-balancer-api-external: resolved host name ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:42:51Z" - latency: 4.71567ms message: 'load-balancer-api-external: tcp connection to ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:41:51Z" - latency: 6.186975ms message: 'load-balancer-api-external: resolved host name ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:41:51Z" - latency: 4.791432ms message: 'load-balancer-api-external: tcp connection to ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:40:51Z" - latency: 6.885446ms message: 'load-balancer-api-external: resolved host name ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:40:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:14:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-204-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-204.ec2.internal uid: 54b78873-9f5a-4785-949d-d3272ad12384 resourceVersion: "26777" uid: df682d6c-58f2-4e97-8284-3694265bd67b spec: sourcePod: network-check-source-7d88cb55d8-b9t7f targetEndpoint: ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T17:20:51Z" message: 'load-balancer-api-internal: tcp connection to ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.195179ms message: 'load-balancer-api-internal: tcp connection to ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:44:51Z" - latency: 7.27016ms message: 'load-balancer-api-internal: resolved host name ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:44:51Z" - latency: 4.474925ms message: 'load-balancer-api-internal: tcp connection to ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:43:51Z" - latency: 6.573558ms message: 'load-balancer-api-internal: resolved host name ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:43:51Z" - latency: 3.995443ms message: 'load-balancer-api-internal: tcp connection to ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:42:51Z" - latency: 7.68534ms message: 'load-balancer-api-internal: resolved host name ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:42:51Z" - latency: 4.71083ms message: 'load-balancer-api-internal: tcp connection to ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:41:51Z" - latency: 6.222827ms message: 'load-balancer-api-internal: resolved host name ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:41:51Z" - latency: 4.745783ms message: 'load-balancer-api-internal: tcp connection to ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:40:51Z" - latency: 6.89878ms message: 'load-balancer-api-internal: resolved host name ac8a25d7908f54bd6bc63edb8b1ec8b3-d9116c55fefb4080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:40:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:14:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-204-to-network-check-target-ip-10-0-134-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-204.ec2.internal uid: 54b78873-9f5a-4785-949d-d3272ad12384 resourceVersion: "25683" uid: 26b697ad-b5a7-48e5-b603-fb525a105c4a spec: sourcePod: network-check-source-7d88cb55d8-b9t7f targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:21:51Z" message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.198377ms message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:42:51Z" - latency: 2.213321ms message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:41:51Z" - latency: 2.068679ms message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:40:51Z" - latency: 2.287327ms message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:39:51Z" - latency: 2.107176ms message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:38:51Z" - latency: 1.898255ms message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:37:51Z" - latency: 2.070866ms message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:36:51Z" - latency: 2.135232ms message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:35:51Z" - latency: 2.437678ms message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:34:51Z" - latency: 2.313424ms message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:33:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:14:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-204-to-network-check-target-ip-10-0-139-204 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-204.ec2.internal uid: 54b78873-9f5a-4785-949d-d3272ad12384 resourceVersion: "25682" uid: eb7fc764-1687-49a3-88a0-738197fbe793 spec: sourcePod: network-check-source-7d88cb55d8-b9t7f targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:21:51Z" message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.333752ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:42:51Z" - latency: 1.174739ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:41:51Z" - latency: 1.23255ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:40:51Z" - latency: 908.109µs message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:39:51Z" - latency: 1.403115ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:38:51Z" - latency: 844.789µs message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:37:51Z" - latency: 1.239873ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:36:51Z" - latency: 942.741µs message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:35:51Z" - latency: 843.591µs message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:34:51Z" - latency: 739.848µs message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:33:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:14:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-204-to-network-check-target-ip-10-0-139-66 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-204.ec2.internal uid: 54b78873-9f5a-4785-949d-d3272ad12384 resourceVersion: "25681" uid: eb5a8280-2c1d-4232-b27b-89cf44f429dd spec: sourcePod: network-check-source-7d88cb55d8-b9t7f targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:21:51Z" message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.618735ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:42:51Z" - latency: 1.852732ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:41:51Z" - latency: 1.893852ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:40:51Z" - latency: 1.776832ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:39:51Z" - latency: 1.779863ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:38:51Z" - latency: 1.907066ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:37:51Z" - latency: 1.740099ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:36:51Z" - latency: 1.737171ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:35:51Z" - latency: 1.786643ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:34:51Z" - latency: 1.819894ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:33:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:14:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-204-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-204.ec2.internal uid: 54b78873-9f5a-4785-949d-d3272ad12384 resourceVersion: "26775" uid: 805187ec-3f65-44f3-afe7-ed875ec1bf40 spec: sourcePod: network-check-source-7d88cb55d8-b9t7f targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T17:20:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 770.925µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:44:51Z" - latency: 1.767402ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:44:51Z" - latency: 813.001µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:43:51Z" - latency: 2.096922ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:43:51Z" - latency: 845.323µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:42:51Z" - latency: 1.779233ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:42:51Z" - latency: 939.935µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:41:51Z" - latency: 1.7951ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:41:51Z" - latency: 992.127µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:40:51Z" - latency: 1.442155ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:40:51Z" kind: List metadata: resourceVersion: ""