apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T05:36:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-189-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-189.ec2.internal uid: 678e93cc-b7d9-42b4-a360-0851194a4b29 resourceVersion: "68187" uid: 7ee600d4-0979-4a61-8098-a2ed959ff272 spec: sourcePod: network-check-source-7bc5b6bf85-nvnxf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-17T05:43:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 973.912µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:25:05Z" - latency: 1.252337ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:24:05Z" - latency: 1.615247ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:23:05Z" - latency: 1.114735ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:22:05Z" - latency: 1.040486ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:21:05Z" - latency: 970.005µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:20:05Z" - latency: 970.111µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:19:05Z" - latency: 881.003µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:18:05Z" - latency: 1.094613ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:17:05Z" - latency: 1.0942ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:16:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T05:36:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-189-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-189.ec2.internal uid: 678e93cc-b7d9-42b4-a360-0851194a4b29 resourceVersion: "67166" uid: d5ff2814-01dd-426e-869e-f25be6fbea01 spec: sourcePod: network-check-source-7bc5b6bf85-nvnxf targetEndpoint: a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T05:42:05Z" message: 'load-balancer-api-external: tcp connection to a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.774511ms message: 'load-balancer-api-external: tcp connection to a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:24:05Z" - latency: 8.614551ms message: 'load-balancer-api-external: resolved host name a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T06:24:05Z" - latency: 5.373664ms message: 'load-balancer-api-external: tcp connection to a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:23:05Z" - latency: 9.097335ms message: 'load-balancer-api-external: resolved host name a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T06:23:05Z" - latency: 6.355556ms message: 'load-balancer-api-external: tcp connection to a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:22:05Z" - latency: 10.316802ms message: 'load-balancer-api-external: resolved host name a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T06:22:05Z" - latency: 4.45528ms message: 'load-balancer-api-external: tcp connection to a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:21:05Z" - latency: 12.450491ms message: 'load-balancer-api-external: resolved host name a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T06:21:05Z" - latency: 16.256119ms message: 'load-balancer-api-external: tcp connection to a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:20:05Z" - latency: 7.928729ms message: 'load-balancer-api-external: resolved host name a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T06:20:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T05:36:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-189-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-189.ec2.internal uid: 678e93cc-b7d9-42b4-a360-0851194a4b29 resourceVersion: "67165" uid: 7ec903e4-ac8e-4128-8bb7-1945e9411753 spec: sourcePod: network-check-source-7bc5b6bf85-nvnxf targetEndpoint: a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T05:42:05Z" message: 'load-balancer-api-internal: tcp connection to a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.220319ms message: 'load-balancer-api-internal: tcp connection to a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:24:05Z" - latency: 8.632837ms message: 'load-balancer-api-internal: resolved host name a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T06:24:05Z" - latency: 5.447667ms message: 'load-balancer-api-internal: tcp connection to a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:23:05Z" - latency: 8.99506ms message: 'load-balancer-api-internal: resolved host name a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T06:23:05Z" - latency: 3.60127ms message: 'load-balancer-api-internal: tcp connection to a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:22:05Z" - latency: 10.36785ms message: 'load-balancer-api-internal: resolved host name a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T06:22:05Z" - latency: 4.490813ms message: 'load-balancer-api-internal: tcp connection to a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:21:05Z" - latency: 12.356817ms message: 'load-balancer-api-internal: resolved host name a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T06:21:05Z" - latency: 4.769005ms message: 'load-balancer-api-internal: tcp connection to a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:20:05Z" - latency: 7.916761ms message: 'load-balancer-api-internal: resolved host name a1009f1017d374b0b8620fda5bdb7e65-8de9e2fe3088c246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T06:20:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T05:36:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-189-to-network-check-target-ip-10-0-128-189 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-189.ec2.internal uid: 678e93cc-b7d9-42b4-a360-0851194a4b29 resourceVersion: "68184" uid: 4ee75a71-2657-4006-a633-01f53af4d04b spec: sourcePod: network-check-source-7bc5b6bf85-nvnxf targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T05:43:05Z" message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.111933ms message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:25:05Z" - latency: 1.143386ms message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:24:05Z" - latency: 942.72µs message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:23:05Z" - latency: 1.084515ms message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:22:05Z" - latency: 997.206µs message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:21:05Z" - latency: 990.677µs message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:20:05Z" - latency: 921.201µs message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:19:05Z" - latency: 1.262179ms message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:18:05Z" - latency: 1.56211ms message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:17:05Z" - latency: 922.908µs message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:16:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T05:36:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-189-to-network-check-target-ip-10-0-128-37 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-189.ec2.internal uid: 678e93cc-b7d9-42b4-a360-0851194a4b29 resourceVersion: "68185" uid: 2f7aa1a9-ec5e-46b2-9a3e-ffb2a426783b spec: sourcePod: network-check-source-7bc5b6bf85-nvnxf targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T05:43:05Z" message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.045366ms message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:25:05Z" - latency: 2.247217ms message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:24:05Z" - latency: 2.439586ms message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:23:05Z" - latency: 2.382688ms message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:22:05Z" - latency: 2.459325ms message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:21:05Z" - latency: 2.405809ms message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:20:05Z" - latency: 2.455858ms message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:19:05Z" - latency: 2.382751ms message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:18:05Z" - latency: 2.338712ms message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:17:05Z" - latency: 2.23308ms message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:16:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T05:36:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-189-to-network-check-target-ip-10-0-142-187 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-189.ec2.internal uid: 678e93cc-b7d9-42b4-a360-0851194a4b29 resourceVersion: "68186" uid: 16eb0d3c-5ca1-4e92-9b99-282d7327c45a spec: sourcePod: network-check-source-7bc5b6bf85-nvnxf targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-17T05:43:05Z" message: 'network-check-target-ip-10-0-142-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.63575ms message: 'network-check-target-ip-10-0-142-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:25:05Z" - latency: 2.347034ms message: 'network-check-target-ip-10-0-142-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:24:05Z" - latency: 3.064565ms message: 'network-check-target-ip-10-0-142-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:23:05Z" - latency: 3.048023ms message: 'network-check-target-ip-10-0-142-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:22:05Z" - latency: 2.590238ms message: 'network-check-target-ip-10-0-142-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:21:05Z" - latency: 2.360891ms message: 'network-check-target-ip-10-0-142-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:20:05Z" - latency: 2.357812ms message: 'network-check-target-ip-10-0-142-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:19:05Z" - latency: 2.635313ms message: 'network-check-target-ip-10-0-142-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:18:05Z" - latency: 2.56474ms message: 'network-check-target-ip-10-0-142-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:17:05Z" - latency: 2.212578ms message: 'network-check-target-ip-10-0-142-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:16:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T05:36:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-189-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-189.ec2.internal uid: 678e93cc-b7d9-42b4-a360-0851194a4b29 resourceVersion: "67163" uid: 5feae34f-ed68-434d-8c40-693227f5f059 spec: sourcePod: network-check-source-7bc5b6bf85-nvnxf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-17T05:42:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.014025ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:24:05Z" - latency: 2.11715ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T06:24:05Z" - latency: 1.07987ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:23:05Z" - latency: 2.006038ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T06:23:05Z" - latency: 914.367µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:22:05Z" - latency: 2.681266ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T06:22:05Z" - latency: 1.084556ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:21:05Z" - latency: 2.296278ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T06:21:05Z" - latency: 816.214µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T06:20:05Z" - latency: 1.723738ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T06:20:05Z" kind: List metadata: resourceVersion: ""