apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-06T19:18:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-200-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-200.ec2.internal uid: e7e92d98-89e4-497f-9504-a76b473a056e resourceVersion: "56315" uid: 92c46485-4b0b-492b-924c-64a6bc4e4400 spec: sourcePod: network-check-source-685456655f-sz7c7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-06T19:25:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 918.245µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:46:45Z" - latency: 1.103507ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:45:45Z" - latency: 1.120584ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:44:45Z" - latency: 1.168231ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:43:45Z" - latency: 1.134042ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:42:45Z" - latency: 1.139183ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:41:45Z" - latency: 937.755µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:40:45Z" - latency: 958.573µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:39:45Z" - latency: 960.741µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:38:45Z" - latency: 1.006633ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:37:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-06T19:18:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-200-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-200.ec2.internal uid: e7e92d98-89e4-497f-9504-a76b473a056e resourceVersion: "58023" uid: 09eb2d5d-8fe3-4125-b9a1-15c5bd627d61 spec: sourcePod: network-check-source-685456655f-sz7c7 targetEndpoint: a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-06T19:24:45Z" message: 'load-balancer-api-external: tcp connection to a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.242759ms message: 'load-balancer-api-external: tcp connection to a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:48:45Z" - latency: 8.242342ms message: 'load-balancer-api-external: resolved host name a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T19:48:45Z" - latency: 4.926239ms message: 'load-balancer-api-external: tcp connection to a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:47:45Z" - latency: 8.519737ms message: 'load-balancer-api-external: resolved host name a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T19:47:45Z" - latency: 4.453967ms message: 'load-balancer-api-external: tcp connection to a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:46:45Z" - latency: 8.997722ms message: 'load-balancer-api-external: resolved host name a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T19:46:45Z" - latency: 5.490984ms message: 'load-balancer-api-external: tcp connection to a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:45:45Z" - latency: 9.860289ms message: 'load-balancer-api-external: resolved host name a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T19:45:45Z" - latency: 4.484299ms message: 'load-balancer-api-external: tcp connection to a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:44:45Z" - latency: 8.964057ms message: 'load-balancer-api-external: resolved host name a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T19:44:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-06T19:18:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-200-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-200.ec2.internal uid: e7e92d98-89e4-497f-9504-a76b473a056e resourceVersion: "58024" uid: 2a1d3f22-91f4-4b72-b206-b96d74c4748b spec: sourcePod: network-check-source-685456655f-sz7c7 targetEndpoint: a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-06T19:24:45Z" message: 'load-balancer-api-internal: tcp connection to a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.20797ms message: 'load-balancer-api-internal: tcp connection to a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:48:45Z" - latency: 8.386665ms message: 'load-balancer-api-internal: resolved host name a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T19:48:45Z" - latency: 4.955407ms message: 'load-balancer-api-internal: tcp connection to a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:47:45Z" - latency: 8.560757ms message: 'load-balancer-api-internal: resolved host name a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T19:47:45Z" - latency: 3.941493ms message: 'load-balancer-api-internal: tcp connection to a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:46:45Z" - latency: 9.093572ms message: 'load-balancer-api-internal: resolved host name a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T19:46:45Z" - latency: 5.475434ms message: 'load-balancer-api-internal: tcp connection to a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:45:45Z" - latency: 9.893848ms message: 'load-balancer-api-internal: resolved host name a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T19:45:45Z" - latency: 4.510874ms message: 'load-balancer-api-internal: tcp connection to a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:44:45Z" - latency: 8.894648ms message: 'load-balancer-api-internal: resolved host name a96c2a47e6ac94b75ba9c6d8dfebf117-854568f81dd58445.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T19:44:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-06T19:18:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-200-to-network-check-target-ip-10-0-129-252 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-200.ec2.internal uid: e7e92d98-89e4-497f-9504-a76b473a056e resourceVersion: "56313" uid: 4f69ebcc-77ae-445f-9d9f-aa8c40add38d spec: sourcePod: network-check-source-685456655f-sz7c7 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-06T19:25:45Z" message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.043822ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:46:45Z" - latency: 2.171654ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:45:45Z" - latency: 2.550543ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:44:45Z" - latency: 2.523114ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:43:45Z" - latency: 2.402098ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:42:45Z" - latency: 2.253227ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:41:45Z" - latency: 2.47447ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:40:45Z" - latency: 2.354163ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:39:45Z" - latency: 2.439414ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:38:45Z" - latency: 2.234735ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:37:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-06T19:18:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-200-to-network-check-target-ip-10-0-135-200 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-200.ec2.internal uid: e7e92d98-89e4-497f-9504-a76b473a056e resourceVersion: "56312" uid: ad704cb5-3868-4939-97bb-cd96502a979e spec: sourcePod: network-check-source-685456655f-sz7c7 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-06T19:25:45Z" message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 985.366µs message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:46:45Z" - latency: 754.936µs message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:45:45Z" - latency: 925.14µs message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:44:45Z" - latency: 1.560677ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:43:45Z" - latency: 1.533712ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:42:45Z" - latency: 1.098051ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:41:45Z" - latency: 948.713µs message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:40:45Z" - latency: 1.223075ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:39:45Z" - latency: 972.786µs message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:38:45Z" - latency: 898.177µs message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:37:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-06T19:18:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-200-to-network-check-target-ip-10-0-135-37 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-200.ec2.internal uid: e7e92d98-89e4-497f-9504-a76b473a056e resourceVersion: "56314" uid: 44d3be68-4ab7-45c7-8fa2-acee5c71cea4 spec: sourcePod: network-check-source-685456655f-sz7c7 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-06T19:25:45Z" message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.373986ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:46:45Z" - latency: 2.266681ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:45:45Z" - latency: 2.133815ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:44:45Z" - latency: 1.92752ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:43:45Z" - latency: 2.49806ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:42:45Z" - latency: 2.349818ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:41:45Z" - latency: 2.297054ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:40:45Z" - latency: 2.272863ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:39:45Z" - latency: 2.326591ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:38:45Z" - latency: 2.506627ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:37:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-06T19:18:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-200-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-200.ec2.internal uid: e7e92d98-89e4-497f-9504-a76b473a056e resourceVersion: "58021" uid: 7a50c4aa-20e4-40da-958c-43b883bc61f3 spec: sourcePod: network-check-source-685456655f-sz7c7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-06T19:24:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.172046ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:48:45Z" - latency: 1.780453ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-06T19:48:45Z" - latency: 1.067001ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:47:45Z" - latency: 1.960017ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-06T19:47:45Z" - latency: 1.036439ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:46:45Z" - latency: 2.179522ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-06T19:46:45Z" - latency: 819.202µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:45:45Z" - latency: 1.796294ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-06T19:45:45Z" - latency: 821.181µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:44:45Z" - latency: 1.851351ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-06T19:44:45Z" kind: List metadata: resourceVersion: ""