apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:28:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-47-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-47.ec2.internal uid: 4bdd545f-bdf3-473c-b555-76ebef7e05f1 resourceVersion: "54585" uid: f36f2d20-87bb-4029-b4e9-1efc5dde5c02 spec: sourcePod: network-check-source-989f8b8dc-k2n9f targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T20:35:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.789974ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:03:36Z" - latency: 1.154051ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:02:36Z" - latency: 910.615µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:01:36Z" - latency: 1.361518ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:00:36Z" - latency: 1.213155ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:59:36Z" - latency: 932.446µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:58:36Z" - latency: 1.555549ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:57:36Z" - latency: 864.464µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:56:36Z" - latency: 823.663µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:55:36Z" - latency: 981.354µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:54:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:28:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-47-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-47.ec2.internal uid: 4bdd545f-bdf3-473c-b555-76ebef7e05f1 resourceVersion: "55509" uid: b85af855-9249-4d19-aebb-9068ff30f90c spec: sourcePod: network-check-source-989f8b8dc-k2n9f targetEndpoint: ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T20:34:36Z" message: 'load-balancer-api-external: tcp connection to ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.701605ms message: 'load-balancer-api-external: tcp connection to ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:04:36Z" - latency: 7.613283ms message: 'load-balancer-api-external: resolved host name ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:04:36Z" - latency: 3.851562ms message: 'load-balancer-api-external: tcp connection to ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:03:36Z" - latency: 9.503862ms message: 'load-balancer-api-external: resolved host name ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:03:36Z" - latency: 5.850975ms message: 'load-balancer-api-external: tcp connection to ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:02:36Z" - latency: 7.658775ms message: 'load-balancer-api-external: resolved host name ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:02:36Z" - latency: 5.849651ms message: 'load-balancer-api-external: tcp connection to ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:01:36Z" - latency: 9.238059ms message: 'load-balancer-api-external: resolved host name ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:01:36Z" - latency: 5.007587ms message: 'load-balancer-api-external: tcp connection to ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:00:36Z" - latency: 8.290617ms message: 'load-balancer-api-external: resolved host name ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:00:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:28:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-47-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-47.ec2.internal uid: 4bdd545f-bdf3-473c-b555-76ebef7e05f1 resourceVersion: "55508" uid: e97ca043-856d-4e61-b99b-693e914a66d3 spec: sourcePod: network-check-source-989f8b8dc-k2n9f targetEndpoint: ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T20:34:36Z" message: 'load-balancer-api-internal: tcp connection to ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.84864ms message: 'load-balancer-api-internal: tcp connection to ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:04:36Z" - latency: 7.571086ms message: 'load-balancer-api-internal: resolved host name ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:04:36Z" - latency: 3.841217ms message: 'load-balancer-api-internal: tcp connection to ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:03:36Z" - latency: 9.685513ms message: 'load-balancer-api-internal: resolved host name ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:03:36Z" - latency: 5.79868ms message: 'load-balancer-api-internal: tcp connection to ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:02:36Z" - latency: 7.570843ms message: 'load-balancer-api-internal: resolved host name ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:02:36Z" - latency: 4.934537ms message: 'load-balancer-api-internal: tcp connection to ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:01:36Z" - latency: 9.334835ms message: 'load-balancer-api-internal: resolved host name ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:01:36Z" - latency: 4.995161ms message: 'load-balancer-api-internal: tcp connection to ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:00:36Z" - latency: 8.252858ms message: 'load-balancer-api-internal: resolved host name ac2109ce2fc874a1c9309d8ebe2b6e1f-2a3d4d873648fda7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:00:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:28:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-47-to-network-check-target-ip-10-0-128-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-47.ec2.internal uid: 4bdd545f-bdf3-473c-b555-76ebef7e05f1 resourceVersion: "54583" uid: a23bd45b-a87e-413b-bff2-7d2dc681171e spec: sourcePod: network-check-source-989f8b8dc-k2n9f targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T20:35:36Z" message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 915.875µs message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:03:36Z" - latency: 1.883964ms message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:02:36Z" - latency: 924.744µs message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:01:36Z" - latency: 1.743191ms message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:00:36Z" - latency: 971.687µs message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:59:36Z" - latency: 1.242384ms message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:58:36Z" - latency: 1.422855ms message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:57:36Z" - latency: 1.742288ms message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:56:36Z" - latency: 838.391µs message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:55:36Z" - latency: 1.002762ms message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:54:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:28:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-47-to-network-check-target-ip-10-0-138-229 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-47.ec2.internal uid: 4bdd545f-bdf3-473c-b555-76ebef7e05f1 resourceVersion: "54584" uid: e3a04bd5-9752-4e60-9b27-e7af5cf86727 spec: sourcePod: network-check-source-989f8b8dc-k2n9f targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T20:35:36Z" message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.384011ms message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:03:36Z" - latency: 2.74978ms message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:02:36Z" - latency: 2.147824ms message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:01:36Z" - latency: 2.820472ms message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:00:36Z" - latency: 2.089276ms message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:59:36Z" - latency: 2.336734ms message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:58:36Z" - latency: 2.457051ms message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:57:36Z" - latency: 2.189781ms message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:56:36Z" - latency: 2.250067ms message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:55:36Z" - latency: 2.334702ms message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:54:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:28:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-47-to-network-check-target-ip-10-0-141-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-47.ec2.internal uid: 4bdd545f-bdf3-473c-b555-76ebef7e05f1 resourceVersion: "54586" uid: 2c55a069-294d-4546-8e6c-b0f0ceb9661f spec: sourcePod: network-check-source-989f8b8dc-k2n9f targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T20:35:36Z" message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.99095ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:03:36Z" - latency: 2.167928ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:02:36Z" - latency: 1.840689ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:01:36Z" - latency: 2.06224ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:00:36Z" - latency: 1.767232ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:59:36Z" - latency: 1.918678ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:58:36Z" - latency: 2.132558ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:57:36Z" - latency: 1.832325ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:56:36Z" - latency: 1.944961ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:55:36Z" - latency: 1.915629ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:54:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:28:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-47-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-47.ec2.internal uid: 4bdd545f-bdf3-473c-b555-76ebef7e05f1 resourceVersion: "55507" uid: 0bdbc5e3-30fd-4b70-be46-f35d0cf2576b spec: sourcePod: network-check-source-989f8b8dc-k2n9f targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T20:34:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 780.153µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:04:36Z" - latency: 1.83228ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:04:36Z" - latency: 832.982µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:03:36Z" - latency: 1.835913ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:03:36Z" - latency: 1.055729ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:02:36Z" - latency: 1.807056ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:02:36Z" - latency: 897.781µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:01:36Z" - latency: 1.939374ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:01:36Z" - latency: 1.374513ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:00:36Z" - latency: 2.099057ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:00:36Z" kind: List metadata: resourceVersion: ""