apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:29:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-206-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-206.ec2.internal uid: e8785e7d-515e-42ce-968e-491aa3d51c70 resourceVersion: "28275" uid: ff17170c-7cf8-447b-8401-9beae7b814f1 spec: sourcePod: network-check-source-56d84b9f44-4lqqr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T15:36:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.752784ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:43:45Z" - latency: 1.591908ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:42:45Z" - latency: 1.247235ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:41:45Z" - latency: 1.043164ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:40:45Z" - latency: 1.040189ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:39:45Z" - latency: 981.859µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:38:45Z" - latency: 1.184117ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:37:45Z" - latency: 1.401343ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:36:45Z" - latency: 1.386067ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:35:45Z" - latency: 1.032591ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:34:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:29:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-206-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-206.ec2.internal uid: e8785e7d-515e-42ce-968e-491aa3d51c70 resourceVersion: "27008" uid: 4047b5c7-e5cd-4982-ae45-187e99c186e3 spec: sourcePod: network-check-source-56d84b9f44-4lqqr targetEndpoint: aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T15:35:45Z" message: 'load-balancer-api-external: tcp connection to aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.182185ms message: 'load-balancer-api-external: tcp connection to aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:41:45Z" - latency: 7.284183ms message: 'load-balancer-api-external: resolved host name aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T15:41:45Z" - latency: 5.222849ms message: 'load-balancer-api-external: tcp connection to aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:40:45Z" - latency: 8.267948ms message: 'load-balancer-api-external: resolved host name aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T15:40:45Z" - latency: 5.490902ms message: 'load-balancer-api-external: tcp connection to aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:39:45Z" - latency: 6.688063ms message: 'load-balancer-api-external: resolved host name aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T15:39:45Z" - latency: 5.998347ms message: 'load-balancer-api-external: tcp connection to aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:38:45Z" - latency: 6.78585ms message: 'load-balancer-api-external: resolved host name aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T15:38:45Z" - latency: 5.316534ms message: 'load-balancer-api-external: tcp connection to aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:37:45Z" - latency: 6.708931ms message: 'load-balancer-api-external: resolved host name aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T15:37:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:29:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-206-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-206.ec2.internal uid: e8785e7d-515e-42ce-968e-491aa3d51c70 resourceVersion: "27006" uid: 153d6617-2290-4535-b28f-fad8caec2360 spec: sourcePod: network-check-source-56d84b9f44-4lqqr targetEndpoint: aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T15:35:45Z" message: 'load-balancer-api-internal: tcp connection to aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.177342ms message: 'load-balancer-api-internal: tcp connection to aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:41:45Z" - latency: 7.185894ms message: 'load-balancer-api-internal: resolved host name aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T15:41:45Z" - latency: 5.235512ms message: 'load-balancer-api-internal: tcp connection to aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:40:45Z" - latency: 8.17368ms message: 'load-balancer-api-internal: resolved host name aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T15:40:45Z" - latency: 5.526702ms message: 'load-balancer-api-internal: tcp connection to aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:39:45Z" - latency: 6.605732ms message: 'load-balancer-api-internal: resolved host name aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T15:39:45Z" - latency: 5.988697ms message: 'load-balancer-api-internal: tcp connection to aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:38:45Z" - latency: 6.830101ms message: 'load-balancer-api-internal: resolved host name aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T15:38:45Z" - latency: 5.308599ms message: 'load-balancer-api-internal: tcp connection to aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:37:45Z" - latency: 6.093786ms message: 'load-balancer-api-internal: resolved host name aa222f4cff05c4918987fb76fcc5312b-96d2c6d2c5c66a5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T15:37:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:29:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-206-to-network-check-target-ip-10-0-136-206 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-206.ec2.internal uid: e8785e7d-515e-42ce-968e-491aa3d51c70 resourceVersion: "28272" uid: 663aafd7-d3c2-4b34-b926-3cdfea81cbcc spec: sourcePod: network-check-source-56d84b9f44-4lqqr targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-02T15:36:45Z" message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 822.667µs message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:43:45Z" - latency: 800.197µs message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:42:45Z" - latency: 907.692µs message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:41:45Z" - latency: 1.20042ms message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:40:45Z" - latency: 841.635µs message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:39:45Z" - latency: 833.539µs message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:38:45Z" - latency: 966.827µs message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:37:45Z" - latency: 1.437997ms message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:36:45Z" - latency: 834.249µs message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:35:45Z" - latency: 1.227877ms message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:34:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:29:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-206-to-network-check-target-ip-10-0-140-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-206.ec2.internal uid: e8785e7d-515e-42ce-968e-491aa3d51c70 resourceVersion: "28273" uid: 2da76c01-5b97-4f67-94a6-37fb891ef26d spec: sourcePod: network-check-source-56d84b9f44-4lqqr targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-02T15:36:45Z" message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.338098ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:43:45Z" - latency: 2.109892ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:42:45Z" - latency: 1.995357ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:41:45Z" - latency: 2.252218ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:40:45Z" - latency: 2.048556ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:39:45Z" - latency: 2.355418ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:38:45Z" - latency: 2.416319ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:37:45Z" - latency: 2.266287ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:36:45Z" - latency: 2.213593ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:35:45Z" - latency: 1.91793ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:34:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:29:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-206-to-network-check-target-ip-10-0-141-151 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-206.ec2.internal uid: e8785e7d-515e-42ce-968e-491aa3d51c70 resourceVersion: "28274" uid: c519d15f-7f60-4a60-b07a-0f174e33f311 spec: sourcePod: network-check-source-56d84b9f44-4lqqr targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T15:36:45Z" message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.019273ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:43:45Z" - latency: 2.373856ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:42:45Z" - latency: 2.338395ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:41:45Z" - latency: 2.195002ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:40:45Z" - latency: 2.25893ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:39:45Z" - latency: 2.305894ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:38:45Z" - latency: 2.459213ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:37:45Z" - latency: 2.350302ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:36:45Z" - latency: 2.286199ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:35:45Z" - latency: 2.330154ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:34:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:29:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-206-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-206.ec2.internal uid: e8785e7d-515e-42ce-968e-491aa3d51c70 resourceVersion: "27005" uid: 20900363-4b85-41b6-b5e7-bcca4ad230b8 spec: sourcePod: network-check-source-56d84b9f44-4lqqr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T15:35:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.06052ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:41:45Z" - latency: 1.855979ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T15:41:45Z" - latency: 1.133716ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:40:45Z" - latency: 1.746426ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T15:40:45Z" - latency: 897.614µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:39:45Z" - latency: 1.597535ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T15:39:45Z" - latency: 808.312µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:38:45Z" - latency: 1.616871ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T15:38:45Z" - latency: 754.413µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:37:45Z" - latency: 1.437292ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T15:37:45Z" kind: List metadata: resourceVersion: ""