apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T18:34:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-27-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-27.ec2.internal uid: 26e4fd3b-f52a-4e0f-a11f-0f0053cccee1 resourceVersion: "21806" uid: 2a273420-0440-44e7-b4e1-cd0b222e5112 spec: sourcePod: network-check-source-989f8b8dc-drlq7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T18:41:48Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.163883ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:55:48Z" - latency: 608.437µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:54:48Z" - latency: 888.978µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:53:48Z" - latency: 1.039956ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:52:48Z" - latency: 1.105086ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:51:48Z" - latency: 995.369µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:50:48Z" - latency: 796.401µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:49:48Z" - latency: 1.257313ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:48:48Z" - latency: 894.106µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:47:48Z" - latency: 1.232695ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:46:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T18:34:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-27-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-27.ec2.internal uid: 26e4fd3b-f52a-4e0f-a11f-0f0053cccee1 resourceVersion: "20379" uid: da344a09-db79-4171-a43a-d21564ed89fc spec: sourcePod: network-check-source-989f8b8dc-drlq7 targetEndpoint: a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T18:40:48Z" message: 'load-balancer-api-external: tcp connection to a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.032265ms message: 'load-balancer-api-external: tcp connection to a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:52:48Z" - latency: 7.794531ms message: 'load-balancer-api-external: resolved host name a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T18:52:48Z" - latency: 5.0014ms message: 'load-balancer-api-external: tcp connection to a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:51:48Z" - latency: 8.603285ms message: 'load-balancer-api-external: resolved host name a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T18:51:48Z" - latency: 5.367044ms message: 'load-balancer-api-external: tcp connection to a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:50:48Z" - latency: 9.423084ms message: 'load-balancer-api-external: resolved host name a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T18:50:48Z" - latency: 5.907467ms message: 'load-balancer-api-external: tcp connection to a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:49:48Z" - latency: 7.371957ms message: 'load-balancer-api-external: resolved host name a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T18:49:48Z" - latency: 5.146237ms message: 'load-balancer-api-external: tcp connection to a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:48:48Z" - latency: 8.892252ms message: 'load-balancer-api-external: resolved host name a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T18:48:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T18:34:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-27-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-27.ec2.internal uid: 26e4fd3b-f52a-4e0f-a11f-0f0053cccee1 resourceVersion: "20380" uid: e6846896-35a1-4d4b-bfed-ff858f7c2d88 spec: sourcePod: network-check-source-989f8b8dc-drlq7 targetEndpoint: a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T18:40:48Z" message: 'load-balancer-api-internal: tcp connection to a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.716524ms message: 'load-balancer-api-internal: tcp connection to a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:52:48Z" - latency: 7.838618ms message: 'load-balancer-api-internal: resolved host name a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T18:52:48Z" - latency: 4.99124ms message: 'load-balancer-api-internal: tcp connection to a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:51:48Z" - latency: 8.641364ms message: 'load-balancer-api-internal: resolved host name a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T18:51:48Z" - latency: 5.371205ms message: 'load-balancer-api-internal: tcp connection to a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:50:48Z" - latency: 9.459931ms message: 'load-balancer-api-internal: resolved host name a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T18:50:48Z" - latency: 5.924491ms message: 'load-balancer-api-internal: tcp connection to a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:49:48Z" - latency: 7.403508ms message: 'load-balancer-api-internal: resolved host name a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T18:49:48Z" - latency: 4.661793ms message: 'load-balancer-api-internal: tcp connection to a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:48:48Z" - latency: 8.945238ms message: 'load-balancer-api-internal: resolved host name a1cf57fc9b11c45ddbde9a3b97d1d89e-b8252b4f34640af6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T18:48:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T18:34:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-27-to-network-check-target-ip-10-0-130-27 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-27.ec2.internal uid: 26e4fd3b-f52a-4e0f-a11f-0f0053cccee1 resourceVersion: "21804" uid: 9312fbc8-4a6d-40d5-a798-b3a01878e643 spec: sourcePod: network-check-source-989f8b8dc-drlq7 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T18:41:48Z" message: 'network-check-target-ip-10-0-130-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.000741ms message: 'network-check-target-ip-10-0-130-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:55:48Z" - latency: 787.848µs message: 'network-check-target-ip-10-0-130-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:54:48Z" - latency: 833.939µs message: 'network-check-target-ip-10-0-130-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:53:48Z" - latency: 1.217499ms message: 'network-check-target-ip-10-0-130-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:52:48Z" - latency: 906.13µs message: 'network-check-target-ip-10-0-130-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:51:48Z" - latency: 1.45398ms message: 'network-check-target-ip-10-0-130-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:50:48Z" - latency: 882.762µs message: 'network-check-target-ip-10-0-130-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:49:48Z" - latency: 880.733µs message: 'network-check-target-ip-10-0-130-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:48:48Z" - latency: 1.29508ms message: 'network-check-target-ip-10-0-130-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:47:48Z" - latency: 902.309µs message: 'network-check-target-ip-10-0-130-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:46:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T18:34:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-27-to-network-check-target-ip-10-0-135-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-27.ec2.internal uid: 26e4fd3b-f52a-4e0f-a11f-0f0053cccee1 resourceVersion: "21803" uid: f68ac880-3499-44a6-96f6-cdbdcf3b2482 spec: sourcePod: network-check-source-989f8b8dc-drlq7 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T18:41:48Z" message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.890671ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:55:48Z" - latency: 1.576764ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:54:48Z" - latency: 2.017205ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:53:48Z" - latency: 2.0959ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:52:48Z" - latency: 1.980743ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:51:48Z" - latency: 2.049636ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:50:48Z" - latency: 1.498277ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:49:48Z" - latency: 1.800386ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:48:48Z" - latency: 1.850828ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:47:48Z" - latency: 2.006465ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:46:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T18:34:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-27-to-network-check-target-ip-10-0-136-219 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-27.ec2.internal uid: 26e4fd3b-f52a-4e0f-a11f-0f0053cccee1 resourceVersion: "21805" uid: aad8eed3-2e85-4da6-8066-4d7c5308f5db spec: sourcePod: network-check-source-989f8b8dc-drlq7 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T18:41:48Z" message: 'network-check-target-ip-10-0-136-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.186871ms message: 'network-check-target-ip-10-0-136-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:55:48Z" - latency: 2.032703ms message: 'network-check-target-ip-10-0-136-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:54:48Z" - latency: 1.873445ms message: 'network-check-target-ip-10-0-136-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:53:48Z" - latency: 2.10576ms message: 'network-check-target-ip-10-0-136-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:52:48Z" - latency: 2.152972ms message: 'network-check-target-ip-10-0-136-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:51:48Z" - latency: 2.224626ms message: 'network-check-target-ip-10-0-136-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:50:48Z" - latency: 2.222034ms message: 'network-check-target-ip-10-0-136-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:49:48Z" - latency: 2.246575ms message: 'network-check-target-ip-10-0-136-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:48:48Z" - latency: 2.210826ms message: 'network-check-target-ip-10-0-136-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:47:48Z" - latency: 2.556734ms message: 'network-check-target-ip-10-0-136-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:46:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T18:34:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-27-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-27.ec2.internal uid: 26e4fd3b-f52a-4e0f-a11f-0f0053cccee1 resourceVersion: "20378" uid: 350a33b6-1714-4438-9238-667ec608ae3e spec: sourcePod: network-check-source-989f8b8dc-drlq7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T18:40:48Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 800.641µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:52:48Z" - latency: 1.705582ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T18:52:48Z" - latency: 829.168µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:51:48Z" - latency: 1.914416ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T18:51:48Z" - latency: 1.119213ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:50:48Z" - latency: 1.889494ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T18:50:48Z" - latency: 838.409µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:49:48Z" - latency: 1.866081ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T18:49:48Z" - latency: 834.368µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T18:48:48Z" - latency: 2.14729ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T18:48:48Z" kind: List metadata: resourceVersion: ""