apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T13:06:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-83-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-83.ec2.internal uid: 60f9bd21-079b-42d5-a328-8dd73d1dee1c resourceVersion: "32140" uid: 9954c370-2a2c-4e6b-8438-dc69a723216b spec: sourcePod: network-check-source-dbd9cf844-f5mh8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-06T13:13:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 913.525µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:20:59Z" - latency: 988.818µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:19:59Z" - latency: 958.356µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:18:59Z" - latency: 1.067606ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:17:59Z" - latency: 1.149522ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:16:59Z" - latency: 1.014827ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:15:59Z" - latency: 1.128028ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:14:59Z" - latency: 752.323µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:13:59Z" - latency: 1.726596ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:12:59Z" - latency: 1.550122ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:11:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T13:06:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-83-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-83.ec2.internal uid: 60f9bd21-079b-42d5-a328-8dd73d1dee1c resourceVersion: "30275" uid: 834bf56e-65a0-48b2-9958-cf3049cd7610 spec: sourcePod: network-check-source-dbd9cf844-f5mh8 targetEndpoint: a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-06T13:12:59Z" message: 'load-balancer-api-external: tcp connection to a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.793435ms message: 'load-balancer-api-external: tcp connection to a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:18:59Z" - latency: 7.399326ms message: 'load-balancer-api-external: resolved host name a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T13:18:59Z" - latency: 5.362652ms message: 'load-balancer-api-external: tcp connection to a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:17:59Z" - latency: 7.578624ms message: 'load-balancer-api-external: resolved host name a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T13:17:59Z" - latency: 5.251567ms message: 'load-balancer-api-external: tcp connection to a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:16:59Z" - latency: 6.342628ms message: 'load-balancer-api-external: resolved host name a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T13:16:59Z" - latency: 4.955558ms message: 'load-balancer-api-external: tcp connection to a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:15:59Z" - latency: 7.68343ms message: 'load-balancer-api-external: resolved host name a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T13:15:59Z" - latency: 4.377514ms message: 'load-balancer-api-external: tcp connection to a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:14:59Z" - latency: 8.3714ms message: 'load-balancer-api-external: resolved host name a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T13:14:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T13:06:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-83-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-83.ec2.internal uid: 60f9bd21-079b-42d5-a328-8dd73d1dee1c resourceVersion: "30276" uid: ee8d7e6f-7442-4b60-bae6-2fbd0d4a1f10 spec: sourcePod: network-check-source-dbd9cf844-f5mh8 targetEndpoint: a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-06T13:12:59Z" message: 'load-balancer-api-internal: tcp connection to a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.130827ms message: 'load-balancer-api-internal: tcp connection to a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:18:59Z" - latency: 7.462415ms message: 'load-balancer-api-internal: resolved host name a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T13:18:59Z" - latency: 5.361808ms message: 'load-balancer-api-internal: tcp connection to a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:17:59Z" - latency: 7.524793ms message: 'load-balancer-api-internal: resolved host name a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T13:17:59Z" - latency: 5.266897ms message: 'load-balancer-api-internal: tcp connection to a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:16:59Z" - latency: 6.393965ms message: 'load-balancer-api-internal: resolved host name a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T13:16:59Z" - latency: 4.999468ms message: 'load-balancer-api-internal: tcp connection to a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:15:59Z" - latency: 7.633338ms message: 'load-balancer-api-internal: resolved host name a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T13:15:59Z" - latency: 3.557627ms message: 'load-balancer-api-internal: tcp connection to a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:14:59Z" - latency: 8.33871ms message: 'load-balancer-api-internal: resolved host name a450ebed579264e61a9701daee7d54e3-0d9203f80e995b90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T13:14:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T13:06:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-83-to-network-check-target-ip-10-0-131-83 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-83.ec2.internal uid: 60f9bd21-079b-42d5-a328-8dd73d1dee1c resourceVersion: "32137" uid: af7d40ab-6cf1-4f94-8f2d-145396952057 spec: sourcePod: network-check-source-dbd9cf844-f5mh8 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-06T13:13:59Z" message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.169451ms message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:20:59Z" - latency: 750.31µs message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:19:59Z" - latency: 768.211µs message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:18:59Z" - latency: 1.036077ms message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:17:59Z" - latency: 763.18µs message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:16:59Z" - latency: 1.285516ms message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:15:59Z" - latency: 1.134439ms message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:14:59Z" - latency: 927.592µs message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:13:59Z" - latency: 852.269µs message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:12:59Z" - latency: 1.525024ms message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:11:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T13:06:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-83-to-network-check-target-ip-10-0-135-184 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-83.ec2.internal uid: 60f9bd21-079b-42d5-a328-8dd73d1dee1c resourceVersion: "32139" uid: 8b9143b4-bc1e-4f53-868f-da04c9ffb905 spec: sourcePod: network-check-source-dbd9cf844-f5mh8 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-06T13:13:59Z" message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.66391ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:20:59Z" - latency: 1.962056ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:19:59Z" - latency: 2.394687ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:18:59Z" - latency: 3.31501ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:17:59Z" - latency: 2.196681ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:16:59Z" - latency: 2.331015ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:15:59Z" - latency: 2.754007ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:14:59Z" - latency: 1.856675ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:13:59Z" - latency: 2.572411ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:12:59Z" - latency: 2.49376ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:11:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T13:06:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-83-to-network-check-target-ip-10-0-140-166 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-83.ec2.internal uid: 60f9bd21-079b-42d5-a328-8dd73d1dee1c resourceVersion: "32138" uid: 1be2b638-3390-45a5-bed2-0526b27f6416 spec: sourcePod: network-check-source-dbd9cf844-f5mh8 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-06T13:13:59Z" message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.320303ms message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:20:59Z" - latency: 2.101268ms message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:19:59Z" - latency: 3.01276ms message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:18:59Z" - latency: 3.292077ms message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:17:59Z" - latency: 2.554928ms message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:16:59Z" - latency: 2.636067ms message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:15:59Z" - latency: 2.796889ms message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:14:59Z" - latency: 2.112135ms message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:13:59Z" - latency: 2.3288ms message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:12:59Z" - latency: 2.390624ms message: 'network-check-target-ip-10-0-140-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:11:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T13:06:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-83-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-83.ec2.internal uid: 60f9bd21-079b-42d5-a328-8dd73d1dee1c resourceVersion: "30274" uid: ab3e1530-4d03-4d4c-a90a-ea4d565963ae spec: sourcePod: network-check-source-dbd9cf844-f5mh8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-06T13:12:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.521316ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:18:59Z" - latency: 2.514718ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T13:18:59Z" - latency: 747.375µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:17:59Z" - latency: 2.104625ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T13:17:59Z" - latency: 921.385µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:16:59Z" - latency: 1.756579ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T13:16:59Z" - latency: 1.036985ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:15:59Z" - latency: 1.741645ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T13:15:59Z" - latency: 901.646µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T13:14:59Z" - latency: 2.732434ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T13:14:59Z" kind: List metadata: resourceVersion: ""