apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T07:26:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-76-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-76.ec2.internal uid: 05a67954-d5ff-487d-ae17-65d0e20dc5fd resourceVersion: "68983" uid: a9a5b823-3180-4c28-9678-4b2ea8ce8799 spec: sourcePod: network-check-source-6f8b768455-j5lqb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-15T07:33: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.197743ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T08:01:05Z" - latency: 1.430202ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T08:00:05Z" - latency: 1.330768ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:59:05Z" - latency: 1.137549ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:58:05Z" - latency: 1.631634ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:57:05Z" - latency: 1.238252ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:56:05Z" - latency: 1.000217ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:55:05Z" - latency: 1.042073ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:54:05Z" - latency: 1.389368ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:53:05Z" - latency: 1.678149ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:52:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T07:26:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-76-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-76.ec2.internal uid: 05a67954-d5ff-487d-ae17-65d0e20dc5fd resourceVersion: "69610" uid: f10bc7f6-0f29-4ff6-90e1-2c4009b60c16 spec: sourcePod: network-check-source-6f8b768455-j5lqb targetEndpoint: a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-15T07:32:05Z" message: 'load-balancer-api-external: tcp connection to a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.895949ms message: 'load-balancer-api-external: tcp connection to a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T08:02:05Z" - latency: 8.983713ms message: 'load-balancer-api-external: resolved host name a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T08:02:05Z" - latency: 3.260046ms message: 'load-balancer-api-external: tcp connection to a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T08:01:05Z" - latency: 8.276321ms message: 'load-balancer-api-external: resolved host name a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T08:01:05Z" - latency: 3.268178ms message: 'load-balancer-api-external: tcp connection to a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T08:00:05Z" - latency: 8.870519ms message: 'load-balancer-api-external: resolved host name a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T08:00:05Z" - latency: 20.12869ms message: 'load-balancer-api-external: tcp connection to a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:59:05Z" - latency: 8.517659ms message: 'load-balancer-api-external: resolved host name a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:59:05Z" - latency: 3.916839ms message: 'load-balancer-api-external: tcp connection to a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:58:05Z" - latency: 9.414004ms message: 'load-balancer-api-external: resolved host name a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:58:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T07:26:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-76-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-76.ec2.internal uid: 05a67954-d5ff-487d-ae17-65d0e20dc5fd resourceVersion: "69611" uid: 60fd00a9-1a9a-4a83-a1ef-664d7cb0eff9 spec: sourcePod: network-check-source-6f8b768455-j5lqb targetEndpoint: a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-15T07:32:05Z" message: 'load-balancer-api-internal: tcp connection to a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.334895ms message: 'load-balancer-api-internal: tcp connection to a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T08:02:05Z" - latency: 8.84797ms message: 'load-balancer-api-internal: resolved host name a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T08:02:05Z" - latency: 3.051148ms message: 'load-balancer-api-internal: tcp connection to a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T08:01:05Z" - latency: 8.219716ms message: 'load-balancer-api-internal: resolved host name a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T08:01:05Z" - latency: 3.299741ms message: 'load-balancer-api-internal: tcp connection to a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T08:00:05Z" - latency: 8.949298ms message: 'load-balancer-api-internal: resolved host name a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T08:00:05Z" - latency: 4.617599ms message: 'load-balancer-api-internal: tcp connection to a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:59:05Z" - latency: 8.710306ms message: 'load-balancer-api-internal: resolved host name a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:59:05Z" - latency: 4.347567ms message: 'load-balancer-api-internal: tcp connection to a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:58:05Z" - latency: 9.351183ms message: 'load-balancer-api-internal: resolved host name a2a464f35e9a44a538e953eb5de3bd64-7d807a0704c87126.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:58:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T07:26:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-76-to-network-check-target-ip-10-0-129-76 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-76.ec2.internal uid: 05a67954-d5ff-487d-ae17-65d0e20dc5fd resourceVersion: "68980" uid: 015f32e8-b233-4604-a03c-4725471a0f7a spec: sourcePod: network-check-source-6f8b768455-j5lqb targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-15T07:33:05Z" message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.426µs message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T08:01:05Z" - latency: 882.907µs message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T08:00:05Z" - latency: 1.786389ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:59:05Z" - latency: 940.611µs message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:58:05Z" - latency: 1.98808ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:57:05Z" - latency: 1.630845ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:56:05Z" - latency: 1.309547ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:55:05Z" - latency: 1.180748ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:54:05Z" - latency: 823.998µs message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:53:05Z" - latency: 952.123µs message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:52:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T07:26:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-76-to-network-check-target-ip-10-0-141-227 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-76.ec2.internal uid: 05a67954-d5ff-487d-ae17-65d0e20dc5fd resourceVersion: "68982" uid: 28be35c0-78ae-47a3-a535-7f6bd41ac33e spec: sourcePod: network-check-source-6f8b768455-j5lqb targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-15T07:33:05Z" message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.404197ms message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T08:01:05Z" - latency: 2.260478ms message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T08:00:05Z" - latency: 2.097371ms message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:59:05Z" - latency: 2.209917ms message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:58:05Z" - latency: 2.633965ms message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:57:05Z" - latency: 3.180914ms message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:56:05Z" - latency: 2.426885ms message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:55:05Z" - latency: 2.595274ms message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:54:05Z" - latency: 2.642311ms message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:53:05Z" - latency: 2.070721ms message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:52:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T07:26:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-76-to-network-check-target-ip-10-0-143-175 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-76.ec2.internal uid: 05a67954-d5ff-487d-ae17-65d0e20dc5fd resourceVersion: "68981" uid: 2dccdd1f-f19e-4184-9552-fd5ccb724d69 spec: sourcePod: network-check-source-6f8b768455-j5lqb targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-15T07:33:05Z" message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.126097ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T08:01:05Z" - latency: 2.512208ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T08:00:05Z" - latency: 2.708135ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:59:05Z" - latency: 2.564333ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:58:05Z" - latency: 2.701055ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:57:05Z" - latency: 2.565553ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:56:05Z" - latency: 2.544901ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:55:05Z" - latency: 2.241101ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:54:05Z" - latency: 2.631379ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:53:05Z" - latency: 2.318738ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:52:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T07:26:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-76-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-76.ec2.internal uid: 05a67954-d5ff-487d-ae17-65d0e20dc5fd resourceVersion: "69609" uid: 8e4d7381-8d0a-4095-944d-b8eee35c6729 spec: sourcePod: network-check-source-6f8b768455-j5lqb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-15T07:32:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.245093ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T08:02:05Z" - latency: 2.133824ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T08:02:05Z" - latency: 1.402667ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T08:01:05Z" - latency: 1.893175ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T08:01:05Z" - latency: 1.547864ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T08:00:05Z" - latency: 1.760031ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T08:00:05Z" - latency: 897.906µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:59:05Z" - latency: 2.396633ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T07:59:05Z" - latency: 845.027µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:58:05Z" - latency: 1.917717ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T07:58:05Z" kind: List metadata: resourceVersion: ""