apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T17:14:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-254-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-254.ec2.internal uid: 03aa294f-baf0-4b88-b190-e50fc4b704ff resourceVersion: "54415" uid: 42aa76e0-f7f3-47ab-9d5a-0ba5517576fc spec: sourcePod: network-check-source-869dcfcdcd-2f69x targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T17:21:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.050051ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:49:05Z" - latency: 769.233µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:48:05Z" - latency: 1.513033ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:47:05Z" - latency: 1.167171ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:46:05Z" - latency: 1.003459ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:45:05Z" - latency: 879.775µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:44:05Z" - latency: 1.604562ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:43:05Z" - latency: 847.291µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:42:05Z" - latency: 978.166µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:41:05Z" - latency: 1.490904ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:40:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T17:14:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-254-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-254.ec2.internal uid: 03aa294f-baf0-4b88-b190-e50fc4b704ff resourceVersion: "55304" uid: 3c4e13f0-cbdc-46b4-9dfe-c394b7c06b6f spec: sourcePod: network-check-source-869dcfcdcd-2f69x targetEndpoint: a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T17:20:05Z" message: 'load-balancer-api-external: tcp connection to a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.269328ms message: 'load-balancer-api-external: tcp connection to a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:50:05Z" - latency: 6.652162ms message: 'load-balancer-api-external: resolved host name a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:50:05Z" - latency: 5.210067ms message: 'load-balancer-api-external: tcp connection to a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:49:05Z" - latency: 6.770724ms message: 'load-balancer-api-external: resolved host name a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:49:05Z" - latency: 4.337643ms message: 'load-balancer-api-external: tcp connection to a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:48:05Z" - latency: 7.422431ms message: 'load-balancer-api-external: resolved host name a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:48:05Z" - latency: 4.498072ms message: 'load-balancer-api-external: tcp connection to a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:47:05Z" - latency: 7.160934ms message: 'load-balancer-api-external: resolved host name a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:47:05Z" - latency: 5.587671ms message: 'load-balancer-api-external: tcp connection to a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:46:05Z" - latency: 7.244895ms message: 'load-balancer-api-external: resolved host name a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:46:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T17:14:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-254-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-254.ec2.internal uid: 03aa294f-baf0-4b88-b190-e50fc4b704ff resourceVersion: "55305" uid: 62dcfbac-b9aa-415c-ae39-523e601d9425 spec: sourcePod: network-check-source-869dcfcdcd-2f69x targetEndpoint: a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T17:20:05Z" message: 'load-balancer-api-internal: tcp connection to a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.252645ms message: 'load-balancer-api-internal: tcp connection to a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:50:05Z" - latency: 6.694277ms message: 'load-balancer-api-internal: resolved host name a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:50:05Z" - latency: 5.201282ms message: 'load-balancer-api-internal: tcp connection to a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:49:05Z" - latency: 6.855911ms message: 'load-balancer-api-internal: resolved host name a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:49:05Z" - latency: 3.747305ms message: 'load-balancer-api-internal: tcp connection to a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:48:05Z" - latency: 7.473731ms message: 'load-balancer-api-internal: resolved host name a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:48:05Z" - latency: 4.545026ms message: 'load-balancer-api-internal: tcp connection to a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:47:05Z" - latency: 7.198219ms message: 'load-balancer-api-internal: resolved host name a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:47:05Z" - latency: 5.581526ms message: 'load-balancer-api-internal: tcp connection to a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:46:05Z" - latency: 7.190143ms message: 'load-balancer-api-internal: resolved host name a521c4b89505149e7b2716655627bf74-93e641cb30080117.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:46:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T17:14:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-254-to-network-check-target-ip-10-0-134-65 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-254.ec2.internal uid: 03aa294f-baf0-4b88-b190-e50fc4b704ff resourceVersion: "54413" uid: bcd168a1-7cfe-4535-83f6-10c04efa0b1a spec: sourcePod: network-check-source-869dcfcdcd-2f69x targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T17:21:05Z" message: 'network-check-target-ip-10-0-134-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.780407ms message: 'network-check-target-ip-10-0-134-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:49:05Z" - latency: 2.454431ms message: 'network-check-target-ip-10-0-134-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:48:05Z" - latency: 2.308253ms message: 'network-check-target-ip-10-0-134-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:47:05Z" - latency: 2.316754ms message: 'network-check-target-ip-10-0-134-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:46:05Z" - latency: 2.036158ms message: 'network-check-target-ip-10-0-134-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:45:05Z" - latency: 2.254824ms message: 'network-check-target-ip-10-0-134-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:44:05Z" - latency: 2.430451ms message: 'network-check-target-ip-10-0-134-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:43:05Z" - latency: 2.324301ms message: 'network-check-target-ip-10-0-134-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:42:05Z" - latency: 2.155647ms message: 'network-check-target-ip-10-0-134-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:41:05Z" - latency: 2.437386ms message: 'network-check-target-ip-10-0-134-65: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:40:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T17:14:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-254-to-network-check-target-ip-10-0-136-254 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-254.ec2.internal uid: 03aa294f-baf0-4b88-b190-e50fc4b704ff resourceVersion: "54411" uid: 056e8b41-fcf9-4d91-8d11-d3bf95adaff1 spec: sourcePod: network-check-source-869dcfcdcd-2f69x targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T17:21:05Z" message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 979.591µs message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:49:05Z" - latency: 1.206233ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:48:05Z" - latency: 965.437µs message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:47:05Z" - latency: 1.001567ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:46:05Z" - latency: 1.041518ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:45:05Z" - latency: 963.928µs message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:44:05Z" - latency: 1.017055ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:43:05Z" - latency: 1.375898ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:42:05Z" - latency: 957.236µs message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:41:05Z" - latency: 905.906µs message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:40:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T17:14:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-254-to-network-check-target-ip-10-0-140-169 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-254.ec2.internal uid: 03aa294f-baf0-4b88-b190-e50fc4b704ff resourceVersion: "54412" uid: 5414c4b2-7182-41df-a58f-f02d38f5ad03 spec: sourcePod: network-check-source-869dcfcdcd-2f69x targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T17:21:05Z" message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.077718ms message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:49:05Z" - latency: 2.207959ms message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:48:05Z" - latency: 1.989267ms message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:47:05Z" - latency: 1.930063ms message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:46:05Z" - latency: 1.977854ms message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:45:05Z" - latency: 2.04151ms message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:44:05Z" - latency: 1.997609ms message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:43:05Z" - latency: 1.711379ms message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:42:05Z" - latency: 1.819252ms message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:41:05Z" - latency: 2.021567ms message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:40:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T17:14:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-254-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-254.ec2.internal uid: 03aa294f-baf0-4b88-b190-e50fc4b704ff resourceVersion: "55303" uid: bb78e33e-e029-4525-a86d-a994a97829cf spec: sourcePod: network-check-source-869dcfcdcd-2f69x targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T17:20:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 935.311µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:50:05Z" - latency: 1.726759ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T17:50:05Z" - latency: 1.222237ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:49:05Z" - latency: 1.933653ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T17:49:05Z" - latency: 858.403µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:48:05Z" - latency: 1.544655ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T17:48:05Z" - latency: 876.069µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:47:05Z" - latency: 2.070723ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T17:47:05Z" - latency: 937.827µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:46:05Z" - latency: 1.756357ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T17:46:05Z" kind: List metadata: resourceVersion: ""