apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T20:32:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-56-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-56.ec2.internal uid: 6b37c6c4-274b-4353-982e-5febb549f7cc resourceVersion: "20797" uid: b0964562-3923-4c51-9fe9-b219eb9a9a03 spec: sourcePod: network-check-source-6947749cfc-bbmh7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T20:39:49Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 905.613µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:53:49Z" - latency: 864.772µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:52:49Z" - latency: 1.111483ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:51:49Z" - latency: 935.152µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:50:49Z" - latency: 1.087942ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:49:49Z" - latency: 966.047µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:48:49Z" - latency: 1.349389ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:47:49Z" - latency: 733.58µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:46:49Z" - latency: 921.238µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:45:49Z" - latency: 908.556µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:44:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T20:32:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-56-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-56.ec2.internal uid: 6b37c6c4-274b-4353-982e-5febb549f7cc resourceVersion: "22241" uid: b2092871-1ba3-43ce-9da5-4c25c03b0221 spec: sourcePod: network-check-source-6947749cfc-bbmh7 targetEndpoint: afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T20:38:49Z" message: 'load-balancer-api-external: tcp connection to afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.047518ms message: 'load-balancer-api-external: tcp connection to afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:56:49Z" - latency: 7.742055ms message: 'load-balancer-api-external: resolved host name afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:56:49Z" - latency: 4.642563ms message: 'load-balancer-api-external: tcp connection to afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:55:49Z" - latency: 8.812048ms message: 'load-balancer-api-external: resolved host name afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:55:49Z" - latency: 4.946841ms message: 'load-balancer-api-external: tcp connection to afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:54:49Z" - latency: 7.796701ms message: 'load-balancer-api-external: resolved host name afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:54:49Z" - latency: 5.055523ms message: 'load-balancer-api-external: tcp connection to afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:53:49Z" - latency: 9.748407ms message: 'load-balancer-api-external: resolved host name afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:53:49Z" - latency: 4.106844ms message: 'load-balancer-api-external: tcp connection to afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:52:49Z" - latency: 7.512399ms message: 'load-balancer-api-external: resolved host name afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:52:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T20:32:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-56-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-56.ec2.internal uid: 6b37c6c4-274b-4353-982e-5febb549f7cc resourceVersion: "22242" uid: 3eedb784-62ff-44d0-ae46-1608912f57fe spec: sourcePod: network-check-source-6947749cfc-bbmh7 targetEndpoint: afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T20:38:49Z" message: 'load-balancer-api-internal: tcp connection to afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.774159ms message: 'load-balancer-api-internal: tcp connection to afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:56:49Z" - latency: 7.693535ms message: 'load-balancer-api-internal: resolved host name afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:56:49Z" - latency: 4.666826ms message: 'load-balancer-api-internal: tcp connection to afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:55:49Z" - latency: 8.908116ms message: 'load-balancer-api-internal: resolved host name afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:55:49Z" - latency: 4.986024ms message: 'load-balancer-api-internal: tcp connection to afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:54:49Z" - latency: 7.754761ms message: 'load-balancer-api-internal: resolved host name afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:54:49Z" - latency: 5.001951ms message: 'load-balancer-api-internal: tcp connection to afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:53:49Z" - latency: 9.804587ms message: 'load-balancer-api-internal: resolved host name afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:53:49Z" - latency: 4.116281ms message: 'load-balancer-api-internal: tcp connection to afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:52:49Z" - latency: 7.44673ms message: 'load-balancer-api-internal: resolved host name afa85728923614627b179677750d1998-8d607eb06d808f03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:52:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T20:32:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-56-to-network-check-target-ip-10-0-132-179 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-56.ec2.internal uid: 6b37c6c4-274b-4353-982e-5febb549f7cc resourceVersion: "20795" uid: ebc3fabe-e6fc-483f-98da-bbf6628d3ff3 spec: sourcePod: network-check-source-6947749cfc-bbmh7 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T20:39:49Z" message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.081945ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:53:49Z" - latency: 2.077235ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:52:49Z" - latency: 2.112105ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:51:49Z" - latency: 2.11208ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:50:49Z" - latency: 1.97228ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:49:49Z" - latency: 2.166897ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:48:49Z" - latency: 1.910639ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:47:49Z" - latency: 1.960394ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:46:49Z" - latency: 2.193883ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:45:49Z" - latency: 2.187734ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:44:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T20:32:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-56-to-network-check-target-ip-10-0-137-254 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-56.ec2.internal uid: 6b37c6c4-274b-4353-982e-5febb549f7cc resourceVersion: "20796" uid: 73c39685-0859-45da-8681-6764a79a981e spec: sourcePod: network-check-source-6947749cfc-bbmh7 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T20:39:49Z" message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.536711ms message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:53:49Z" - latency: 2.251398ms message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:52:49Z" - latency: 2.117259ms message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:51:49Z" - latency: 1.903057ms message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:50:49Z" - latency: 2.229603ms message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:49:49Z" - latency: 2.093469ms message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:48:49Z" - latency: 2.091539ms message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:47:49Z" - latency: 2.249351ms message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:46:49Z" - latency: 2.133041ms message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:45:49Z" - latency: 2.329589ms message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:44:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T20:32:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-56-to-network-check-target-ip-10-0-141-56 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-56.ec2.internal uid: 6b37c6c4-274b-4353-982e-5febb549f7cc resourceVersion: "20794" uid: 012887fc-ea1f-4661-bc82-40887465954c spec: sourcePod: network-check-source-6947749cfc-bbmh7 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T20:39:49Z" message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 857.21µs message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:53:49Z" - latency: 802.9µs message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:52:49Z" - latency: 1.344098ms message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:51:49Z" - latency: 863.81µs message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:50:49Z" - latency: 801.049µs message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:49:49Z" - latency: 853.591µs message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:48:49Z" - latency: 1.339108ms message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:47:49Z" - latency: 835.983µs message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:46:49Z" - latency: 906.05µs message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:45:49Z" - latency: 763.383µs message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:44:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T20:32:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-56-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-56.ec2.internal uid: 6b37c6c4-274b-4353-982e-5febb549f7cc resourceVersion: "22240" uid: 482614ec-4b76-4b81-8ff6-b5f99d501a05 spec: sourcePod: network-check-source-6947749cfc-bbmh7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T20:38:49Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 828.492µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:56:49Z" - latency: 1.700349ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T20:56:49Z" - latency: 704.233µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:55:49Z" - latency: 1.589011ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T20:55:49Z" - latency: 811.649µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:54:49Z" - latency: 1.695689ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T20:54:49Z" - latency: 671.079µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:53:49Z" - latency: 1.777505ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T20:53:49Z" - latency: 674.155µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:52:49Z" - latency: 1.497579ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T20:52:49Z" kind: List metadata: resourceVersion: ""