apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T23:03:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-182-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-182.ec2.internal uid: 28a4f8c5-2652-47a0-9bf8-f1a564f0ede4 resourceVersion: "36888" uid: 150897a8-b705-419d-9005-d766585a338c spec: sourcePod: network-check-source-685456655f-h949s targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-07T23:10:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 983.43µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:31:25Z" - latency: 1.02021ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:30:25Z" - latency: 949.439µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:29:25Z" - latency: 1.177452ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:28:25Z" - latency: 1.026969ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:27:25Z" - latency: 972.547µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:26:25Z" - latency: 900.484µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:25:25Z" - latency: 1.008395ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:24:25Z" - latency: 1.03481ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:23:25Z" - latency: 1.11909ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:22:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T23:03:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-182-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-182.ec2.internal uid: 28a4f8c5-2652-47a0-9bf8-f1a564f0ede4 resourceVersion: "38165" uid: fca07ec4-a53b-4cc3-bde2-5e8c2f3fbe02 spec: sourcePod: network-check-source-685456655f-h949s targetEndpoint: a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-07T23:09:25Z" message: 'load-balancer-api-external: tcp connection to a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.212495ms message: 'load-balancer-api-external: tcp connection to a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:33:25Z" - latency: 8.055865ms message: 'load-balancer-api-external: resolved host name a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T23:33:25Z" - latency: 4.938749ms message: 'load-balancer-api-external: tcp connection to a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:32:25Z" - latency: 8.857245ms message: 'load-balancer-api-external: resolved host name a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T23:32:25Z" - latency: 4.489475ms message: 'load-balancer-api-external: tcp connection to a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:31:25Z" - latency: 8.285469ms message: 'load-balancer-api-external: resolved host name a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T23:31:25Z" - latency: 5.298391ms message: 'load-balancer-api-external: tcp connection to a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:30:25Z" - latency: 8.204687ms message: 'load-balancer-api-external: resolved host name a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T23:30:25Z" - latency: 5.499994ms message: 'load-balancer-api-external: tcp connection to a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:29:25Z" - latency: 8.382165ms message: 'load-balancer-api-external: resolved host name a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T23:29:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T23:03:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-182-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-182.ec2.internal uid: 28a4f8c5-2652-47a0-9bf8-f1a564f0ede4 resourceVersion: "38164" uid: 5e7ebd1c-6360-4851-bb5f-ac263dcd7908 spec: sourcePod: network-check-source-685456655f-h949s targetEndpoint: a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-07T23:09:25Z" message: 'load-balancer-api-internal: tcp connection to a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.272617ms message: 'load-balancer-api-internal: tcp connection to a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:33:25Z" - latency: 8.148267ms message: 'load-balancer-api-internal: resolved host name a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T23:33:25Z" - latency: 4.929508ms message: 'load-balancer-api-internal: tcp connection to a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:32:25Z" - latency: 8.825559ms message: 'load-balancer-api-internal: resolved host name a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T23:32:25Z" - latency: 4.629773ms message: 'load-balancer-api-internal: tcp connection to a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:31:25Z" - latency: 8.209689ms message: 'load-balancer-api-internal: resolved host name a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T23:31:25Z" - latency: 5.304517ms message: 'load-balancer-api-internal: tcp connection to a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:30:25Z" - latency: 8.153517ms message: 'load-balancer-api-internal: resolved host name a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T23:30:25Z" - latency: 6.399404ms message: 'load-balancer-api-internal: tcp connection to a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:29:25Z" - latency: 8.415604ms message: 'load-balancer-api-internal: resolved host name a60133757d02a462684ad2e3e2362fd0-6f9618e0858e9f7c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T23:29:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T23:03:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-182-to-network-check-target-ip-10-0-133-218 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-182.ec2.internal uid: 28a4f8c5-2652-47a0-9bf8-f1a564f0ede4 resourceVersion: "36887" uid: 9314ffbd-b79c-4dcf-805a-0d4b888def62 spec: sourcePod: network-check-source-685456655f-h949s targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-07T23:10:25Z" message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.356674ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:31:25Z" - latency: 1.948026ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:30:25Z" - latency: 1.967567ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:29:25Z" - latency: 2.228244ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:28:25Z" - latency: 2.886614ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:27:25Z" - latency: 2.424864ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:26:25Z" - latency: 2.110812ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:25:25Z" - latency: 2.062692ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:24:25Z" - latency: 2.232211ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:23:25Z" - latency: 2.251551ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:22:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T23:03:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-182-to-network-check-target-ip-10-0-136-182 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-182.ec2.internal uid: 28a4f8c5-2652-47a0-9bf8-f1a564f0ede4 resourceVersion: "36885" uid: a40dcfca-ae9d-447e-8cd4-bdeef851efec spec: sourcePod: network-check-source-685456655f-h949s targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-07T23:10:25Z" message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 927.006µs message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:31:25Z" - latency: 977.621µs message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:30:25Z" - latency: 1.307042ms message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:29:25Z" - latency: 1.345139ms message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:28:25Z" - latency: 1.32876ms message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:27:25Z" - latency: 887.278µs message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:26:25Z" - latency: 1.287153ms message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:25:25Z" - latency: 1.088267ms message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:24:25Z" - latency: 951.2µs message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:23:25Z" - latency: 781.3µs message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:22:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T23:03:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-182-to-network-check-target-ip-10-0-141-58 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-182.ec2.internal uid: 28a4f8c5-2652-47a0-9bf8-f1a564f0ede4 resourceVersion: "36886" uid: 09838e9b-3556-474c-b5c6-2cda72ef2c51 spec: sourcePod: network-check-source-685456655f-h949s targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-07T23:10:25Z" message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.574211ms message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:31:25Z" - latency: 2.515238ms message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:30:25Z" - latency: 2.462623ms message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:29:25Z" - latency: 2.460508ms message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:28:25Z" - latency: 2.290912ms message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:27:25Z" - latency: 2.307627ms message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:26:25Z" - latency: 2.451584ms message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:25:25Z" - latency: 2.516922ms message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:24:25Z" - latency: 2.221348ms message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:23:25Z" - latency: 2.359574ms message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:22:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T23:03:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-182-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-182.ec2.internal uid: 28a4f8c5-2652-47a0-9bf8-f1a564f0ede4 resourceVersion: "38163" uid: 820a4647-2ff0-4dc7-b13b-643eea266cb6 spec: sourcePod: network-check-source-685456655f-h949s targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-07T23:09:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.164921ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:33:25Z" - latency: 1.732418ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T23:33:25Z" - latency: 830.758µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:32:25Z" - latency: 1.7372ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T23:32:25Z" - latency: 1.001964ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:31:25Z" - latency: 1.777762ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T23:31:25Z" - latency: 1.306722ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:30:25Z" - latency: 2.110136ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T23:30:25Z" - latency: 753.207µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T23:29:25Z" - latency: 1.779291ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T23:29:25Z" kind: List metadata: resourceVersion: ""