apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:23:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-221-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-221.ec2.internal uid: 8dabb53e-9c3a-455e-8f80-2fad3f16ae0b resourceVersion: "21790" uid: 9e1ae985-6a74-477b-a09b-ec7a2b85a085 spec: sourcePod: network-check-source-56499946bc-dg529 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-01T18:30:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 872.764µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:30:56Z" - latency: 1.231806ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:29:56Z" - latency: 810.181µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:28:56Z" - latency: 1.099883ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:27:56Z" - latency: 976.445µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:26:56Z" - latency: 857.188µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:25:56Z" - latency: 1.375853ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:24:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:23:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-221-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-221.ec2.internal uid: 8dabb53e-9c3a-455e-8f80-2fad3f16ae0b resourceVersion: "20656" uid: 4400072d-df2d-4d16-a184-a45ffd73513d spec: sourcePod: network-check-source-56499946bc-dg529 targetEndpoint: a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T18:29:56Z" message: 'load-balancer-api-external: tcp connection to a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.918747ms message: 'load-balancer-api-external: tcp connection to a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:29:56Z" - latency: 15.090529ms message: 'load-balancer-api-external: resolved host name a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:29:56Z" - latency: 5.17771ms message: 'load-balancer-api-external: tcp connection to a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:28:56Z" - latency: 5.954147ms message: 'load-balancer-api-external: resolved host name a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:28:56Z" - latency: 4.525842ms message: 'load-balancer-api-external: tcp connection to a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:27:56Z" - latency: 7.593649ms message: 'load-balancer-api-external: resolved host name a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:27:56Z" - latency: 4.958978ms message: 'load-balancer-api-external: tcp connection to a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:26:56Z" - latency: 7.050116ms message: 'load-balancer-api-external: resolved host name a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:26:56Z" - latency: 5.433984ms message: 'load-balancer-api-external: tcp connection to a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:25:56Z" - latency: 6.39612ms message: 'load-balancer-api-external: resolved host name a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:25:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:23:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-221-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-221.ec2.internal uid: 8dabb53e-9c3a-455e-8f80-2fad3f16ae0b resourceVersion: "20657" uid: a8224d37-7efc-41b5-80ed-5a975304aa87 spec: sourcePod: network-check-source-56499946bc-dg529 targetEndpoint: a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T18:29:56Z" message: 'load-balancer-api-internal: tcp connection to a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.966636ms message: 'load-balancer-api-internal: tcp connection to a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:29:56Z" - latency: 14.969586ms message: 'load-balancer-api-internal: resolved host name a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:29:56Z" - latency: 5.952905ms message: 'load-balancer-api-internal: tcp connection to a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:28:56Z" - latency: 5.898944ms message: 'load-balancer-api-internal: resolved host name a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:28:56Z" - latency: 4.542943ms message: 'load-balancer-api-internal: tcp connection to a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:27:56Z" - latency: 7.616497ms message: 'load-balancer-api-internal: resolved host name a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:27:56Z" - latency: 6.227951ms message: 'load-balancer-api-internal: tcp connection to a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:26:56Z" - latency: 7.004306ms message: 'load-balancer-api-internal: resolved host name a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:26:56Z" - latency: 4.270407ms message: 'load-balancer-api-internal: tcp connection to a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:25:56Z" - latency: 6.312797ms message: 'load-balancer-api-internal: resolved host name a76bbc1c6c67c4a22958acef563e3713-632cc5e59bbe4363.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:25:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:23:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-221-to-network-check-target-ip-10-0-130-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-221.ec2.internal uid: 8dabb53e-9c3a-455e-8f80-2fad3f16ae0b resourceVersion: "21786" uid: 9a2ce744-e8d3-4d79-a0fb-34b65e6d91c8 spec: sourcePod: network-check-source-56499946bc-dg529 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-01T18:30:56Z" message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.009966ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:30:56Z" - latency: 796.01µs message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:29:56Z" - latency: 1.072371ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:28:56Z" - latency: 712.368µs message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:27:56Z" - latency: 803.108µs message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:26:56Z" - latency: 664.076µs message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:25:56Z" - latency: 2.055131ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:24:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:23:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-221-to-network-check-target-ip-10-0-135-33 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-221.ec2.internal uid: 8dabb53e-9c3a-455e-8f80-2fad3f16ae0b resourceVersion: "21788" uid: b49e4a56-8033-4f77-86ca-ca21c476ab59 spec: sourcePod: network-check-source-56499946bc-dg529 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-01T18:30:56Z" message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.944046ms message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:30:56Z" - latency: 10.847377ms message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:29:56Z" - latency: 1.78647ms message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:28:56Z" - latency: 1.636283ms message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:27:56Z" - latency: 1.666566ms message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:26:56Z" - latency: 1.845698ms message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:25:56Z" - latency: 1.970936ms message: 'network-check-target-ip-10-0-135-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:24:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:23:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-221-to-network-check-target-ip-10-0-141-75 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-221.ec2.internal uid: 8dabb53e-9c3a-455e-8f80-2fad3f16ae0b resourceVersion: "21787" uid: 09184db0-58ba-4604-bf9c-6915afe06a42 spec: sourcePod: network-check-source-56499946bc-dg529 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-01T18:30:56Z" message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.975916ms message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:30:56Z" - latency: 3.048678ms message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:29:56Z" - latency: 2.048859ms message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:28:56Z" - latency: 1.955016ms message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:27:56Z" - latency: 1.960787ms message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:26:56Z" - latency: 1.88495ms message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:25:56Z" - latency: 2.204245ms message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:24:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:23:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-221-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-221.ec2.internal uid: 8dabb53e-9c3a-455e-8f80-2fad3f16ae0b resourceVersion: "20655" uid: 92bc88cb-83ec-48da-b092-1ef64d3c2164 spec: sourcePod: network-check-source-56499946bc-dg529 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-01T18:29:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 8.606167ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:29:56Z" - latency: 2.718742ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T18:29:56Z" - latency: 1.015898ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:28:56Z" - latency: 1.766186ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T18:28:56Z" - latency: 1.00926ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:27:56Z" - latency: 1.662034ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T18:27:56Z" - latency: 750.56µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:26:56Z" - latency: 2.134391ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T18:26:56Z" - latency: 783.316µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:25:56Z" - latency: 1.696009ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T18:25:56Z" kind: List metadata: resourceVersion: ""