apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T05:34:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-106-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-106.ec2.internal uid: 49c1dbf8-c6f4-47b2-8955-58376e0a2b0f resourceVersion: "32163" uid: ab82ea03-2133-464c-ac15-cfbbac5efa80 spec: sourcePod: network-check-source-dbd9cf844-jkwbm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T05: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: 1.391094ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:48:41Z" - latency: 1.160768ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:47:41Z" - latency: 1.160964ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:46:41Z" - latency: 815.399µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:45:41Z" - latency: 948.685µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:44:41Z" - latency: 1.026783ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:43:41Z" - latency: 928.783µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:42:41Z" - latency: 1.016664ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:41:41Z" - latency: 1.029871ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:40:41Z" - latency: 901.25µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:39:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T05:34:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-106-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-106.ec2.internal uid: 49c1dbf8-c6f4-47b2-8955-58376e0a2b0f resourceVersion: "35810" uid: 7326b2d4-31c3-4e52-8e96-9c0916224626 spec: sourcePod: network-check-source-dbd9cf844-jkwbm targetEndpoint: ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T05:40:41Z" message: 'load-balancer-api-external: tcp connection to ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.096698ms message: 'load-balancer-api-external: tcp connection to ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:52:41Z" - latency: 8.934582ms message: 'load-balancer-api-external: resolved host name ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T05:52:41Z" - latency: 4.996034ms message: 'load-balancer-api-external: tcp connection to ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:51:41Z" - latency: 8.582015ms message: 'load-balancer-api-external: resolved host name ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T05:51:41Z" - latency: 5.255522ms message: 'load-balancer-api-external: tcp connection to ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:50:41Z" - latency: 10.172494ms message: 'load-balancer-api-external: resolved host name ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T05:50:41Z" - latency: 4.545186ms message: 'load-balancer-api-external: tcp connection to ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:49:41Z" - latency: 11.629296ms message: 'load-balancer-api-external: resolved host name ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T05:49:41Z" - latency: 5.06394ms message: 'load-balancer-api-external: tcp connection to ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:48:41Z" - latency: 10.551523ms message: 'load-balancer-api-external: resolved host name ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T05:48:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T05:34:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-106-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-106.ec2.internal uid: 49c1dbf8-c6f4-47b2-8955-58376e0a2b0f resourceVersion: "35811" uid: f752dd39-6b05-4207-b680-abb8709af434 spec: sourcePod: network-check-source-dbd9cf844-jkwbm targetEndpoint: ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T05:40:41Z" message: 'load-balancer-api-internal: tcp connection to ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.740085ms message: 'load-balancer-api-internal: tcp connection to ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:52:41Z" - latency: 8.966488ms message: 'load-balancer-api-internal: resolved host name ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T05:52:41Z" - latency: 5.00893ms message: 'load-balancer-api-internal: tcp connection to ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:51:41Z" - latency: 8.609528ms message: 'load-balancer-api-internal: resolved host name ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T05:51:41Z" - latency: 4.455884ms message: 'load-balancer-api-internal: tcp connection to ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:50:41Z" - latency: 10.207343ms message: 'load-balancer-api-internal: resolved host name ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T05:50:41Z" - latency: 5.235201ms message: 'load-balancer-api-internal: tcp connection to ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:49:41Z" - latency: 11.549422ms message: 'load-balancer-api-internal: resolved host name ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T05:49:41Z" - latency: 5.594889ms message: 'load-balancer-api-internal: tcp connection to ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:48:41Z" - latency: 10.577734ms message: 'load-balancer-api-internal: resolved host name ac84decc6e0464d9e93c99eef21bd0a2-98d2bdf9e2fc6cfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T05:48:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T05:34:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-106-to-network-check-target-ip-10-0-130-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-106.ec2.internal uid: 49c1dbf8-c6f4-47b2-8955-58376e0a2b0f resourceVersion: "32160" uid: 5f5d5151-9d5e-4492-8e5f-8c6857a90d65 spec: sourcePod: network-check-source-dbd9cf844-jkwbm targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T05:41:41Z" message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.465662ms message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:48:41Z" - latency: 911.358µs message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:47:41Z" - latency: 826.291µs message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:46:41Z" - latency: 1.266331ms message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:45:41Z" - latency: 1.055968ms message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:44:41Z" - latency: 1.117118ms message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:43:41Z" - latency: 1.083865ms message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:42:41Z" - latency: 890.007µs message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:41:41Z" - latency: 981.737µs message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:40:41Z" - latency: 918.466µs message: 'network-check-target-ip-10-0-130-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:39:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T05:34:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-106-to-network-check-target-ip-10-0-135-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-106.ec2.internal uid: 49c1dbf8-c6f4-47b2-8955-58376e0a2b0f resourceVersion: "32162" uid: 5f84ece6-8790-4e23-9f48-0168cc11399a spec: sourcePod: network-check-source-dbd9cf844-jkwbm targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T05:41:41Z" message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.472348ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:48:41Z" - latency: 1.941638ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:47:41Z" - latency: 1.93881ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:46:41Z" - latency: 1.513184ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:45:41Z" - latency: 2.022874ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:44:41Z" - latency: 1.980294ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:43:41Z" - latency: 1.813723ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:42:41Z" - latency: 2.026623ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:41:41Z" - latency: 2.181519ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:40:41Z" - latency: 1.65598ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:39:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T05:34:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-106-to-network-check-target-ip-10-0-135-223 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-106.ec2.internal uid: 49c1dbf8-c6f4-47b2-8955-58376e0a2b0f resourceVersion: "32161" uid: 9bd6d846-fb59-436f-8727-d0f8b96d39e6 spec: sourcePod: network-check-source-dbd9cf844-jkwbm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T05:41:41Z" message: 'network-check-target-ip-10-0-135-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.455083ms message: 'network-check-target-ip-10-0-135-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:48:41Z" - latency: 2.130153ms message: 'network-check-target-ip-10-0-135-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:47:41Z" - latency: 2.426847ms message: 'network-check-target-ip-10-0-135-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:46:41Z" - latency: 2.091075ms message: 'network-check-target-ip-10-0-135-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:45:41Z" - latency: 2.149031ms message: 'network-check-target-ip-10-0-135-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:44:41Z" - latency: 2.163318ms message: 'network-check-target-ip-10-0-135-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:43:41Z" - latency: 2.182444ms message: 'network-check-target-ip-10-0-135-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:42:41Z" - latency: 2.0376ms message: 'network-check-target-ip-10-0-135-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:41:41Z" - latency: 1.820529ms message: 'network-check-target-ip-10-0-135-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:40:41Z" - latency: 2.309299ms message: 'network-check-target-ip-10-0-135-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:39:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T05:34:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-106-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-106.ec2.internal uid: 49c1dbf8-c6f4-47b2-8955-58376e0a2b0f resourceVersion: "35809" uid: e1003cfa-6525-4340-bc32-8940b2954790 spec: sourcePod: network-check-source-dbd9cf844-jkwbm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T05: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.003022ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:52:41Z" - latency: 1.809968ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T05:52:41Z" - latency: 839.89µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:51:41Z" - latency: 1.943236ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T05:51:41Z" - latency: 980.817µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:50:41Z" - latency: 1.927631ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T05:50:41Z" - latency: 995.424µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:49:41Z" - latency: 2.234701ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T05:49:41Z" - latency: 1.135524ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T05:48:41Z" - latency: 2.424875ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T05:48:41Z" kind: List metadata: resourceVersion: ""