apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T19:24:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-2-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-2.ec2.internal uid: b09549a5-dfef-4fd6-9506-82134d329109 resourceVersion: "56390" uid: ca18ca96-b468-4c63-91df-260a3047227d spec: sourcePod: network-check-source-7bc5b6bf85-4lf8g targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-23T19:31:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 790.98µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:59:24Z" - latency: 721.214µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:58:24Z" - latency: 803.971µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:57:24Z" - latency: 754.732µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:56:24Z" - latency: 908.493µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:55:24Z" - latency: 1.030222ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:54:24Z" - latency: 698.165µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:53:24Z" - latency: 1.099698ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:52:24Z" - latency: 1.104564ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:51:24Z" - latency: 951.505µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:50:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T19:24:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-2-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-2.ec2.internal uid: b09549a5-dfef-4fd6-9506-82134d329109 resourceVersion: "57859" uid: d5e4ac9f-a5e0-4362-97ac-f5e5b4fda2ca spec: sourcePod: network-check-source-7bc5b6bf85-4lf8g targetEndpoint: a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T19:30:24Z" message: 'load-balancer-api-external: tcp connection to a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.89119ms message: 'load-balancer-api-external: tcp connection to a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T20:00:24Z" - latency: 7.669849ms message: 'load-balancer-api-external: resolved host name a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T20:00:24Z" - latency: 4.30044ms message: 'load-balancer-api-external: tcp connection to a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:59:24Z" - latency: 8.474145ms message: 'load-balancer-api-external: resolved host name a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T19:59:24Z" - latency: 3.784401ms message: 'load-balancer-api-external: tcp connection to a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:58:24Z" - latency: 8.328043ms message: 'load-balancer-api-external: resolved host name a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T19:58:24Z" - latency: 4.908351ms message: 'load-balancer-api-external: tcp connection to a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:57:24Z" - latency: 7.402026ms message: 'load-balancer-api-external: resolved host name a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T19:57:24Z" - latency: 4.209187ms message: 'load-balancer-api-external: tcp connection to a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:56:24Z" - latency: 8.809619ms message: 'load-balancer-api-external: resolved host name a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T19:56:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T19:24:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-2-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-2.ec2.internal uid: b09549a5-dfef-4fd6-9506-82134d329109 resourceVersion: "57860" uid: d303048e-e620-4c93-a0d9-7cd00b334534 spec: sourcePod: network-check-source-7bc5b6bf85-4lf8g targetEndpoint: a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T19:30:24Z" message: 'load-balancer-api-internal: tcp connection to a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.913405ms message: 'load-balancer-api-internal: tcp connection to a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T20:00:24Z" - latency: 7.636443ms message: 'load-balancer-api-internal: resolved host name a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T20:00:24Z" - latency: 4.288808ms message: 'load-balancer-api-internal: tcp connection to a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:59:24Z" - latency: 8.449323ms message: 'load-balancer-api-internal: resolved host name a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T19:59:24Z" - latency: 4.336912ms message: 'load-balancer-api-internal: tcp connection to a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:58:24Z" - latency: 8.307823ms message: 'load-balancer-api-internal: resolved host name a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T19:58:24Z" - latency: 4.165481ms message: 'load-balancer-api-internal: tcp connection to a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:57:24Z" - latency: 7.332314ms message: 'load-balancer-api-internal: resolved host name a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T19:57:24Z" - latency: 4.203631ms message: 'load-balancer-api-internal: tcp connection to a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:56:24Z" - latency: 8.766723ms message: 'load-balancer-api-internal: resolved host name a519ba31cf28b4301934741e62b1aae9-1d72a1b180139a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T19:56:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T19:24:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-2-to-network-check-target-ip-10-0-129-2 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-2.ec2.internal uid: b09549a5-dfef-4fd6-9506-82134d329109 resourceVersion: "56387" uid: ff290ccd-940b-4297-a749-6b0405909677 spec: sourcePod: network-check-source-7bc5b6bf85-4lf8g targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T19:31:24Z" message: 'network-check-target-ip-10-0-129-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.098597ms message: 'network-check-target-ip-10-0-129-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:59:24Z" - latency: 917.426µs message: 'network-check-target-ip-10-0-129-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:58:24Z" - latency: 774.269µs message: 'network-check-target-ip-10-0-129-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:57:24Z" - latency: 1.490842ms message: 'network-check-target-ip-10-0-129-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:56:24Z" - latency: 762.587µs message: 'network-check-target-ip-10-0-129-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:55:24Z" - latency: 787.854µs message: 'network-check-target-ip-10-0-129-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:54:24Z" - latency: 1.091464ms message: 'network-check-target-ip-10-0-129-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:53:24Z" - latency: 979.134µs message: 'network-check-target-ip-10-0-129-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:52:24Z" - latency: 858.264µs message: 'network-check-target-ip-10-0-129-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:51:24Z" - latency: 1.340138ms message: 'network-check-target-ip-10-0-129-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:50:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T19:24:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-2-to-network-check-target-ip-10-0-135-62 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-2.ec2.internal uid: b09549a5-dfef-4fd6-9506-82134d329109 resourceVersion: "56388" uid: 259b31ee-ba60-4970-8e51-8f3629312f7f spec: sourcePod: network-check-source-7bc5b6bf85-4lf8g targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-23T19:31:24Z" message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.959753ms message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:59:24Z" - latency: 1.944906ms message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:58:24Z" - latency: 1.591914ms message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:57:24Z" - latency: 1.801245ms message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:56:24Z" - latency: 1.834958ms message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:55:24Z" - latency: 1.741484ms message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:54:24Z" - latency: 1.80114ms message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:53:24Z" - latency: 1.809163ms message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:52:24Z" - latency: 1.964745ms message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:51:24Z" - latency: 1.858125ms message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:50:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T19:24:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-2-to-network-check-target-ip-10-0-141-53 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-2.ec2.internal uid: b09549a5-dfef-4fd6-9506-82134d329109 resourceVersion: "56389" uid: fadbd818-ec61-440a-b2e7-07b928f6dd1d spec: sourcePod: network-check-source-7bc5b6bf85-4lf8g targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T19:31:24Z" message: 'network-check-target-ip-10-0-141-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.110286ms message: 'network-check-target-ip-10-0-141-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:59:24Z" - latency: 2.348387ms message: 'network-check-target-ip-10-0-141-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:58:24Z" - latency: 1.671074ms message: 'network-check-target-ip-10-0-141-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:57:24Z" - latency: 2.439692ms message: 'network-check-target-ip-10-0-141-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:56:24Z" - latency: 2.13287ms message: 'network-check-target-ip-10-0-141-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:55:24Z" - latency: 2.186111ms message: 'network-check-target-ip-10-0-141-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:54:24Z" - latency: 2.273813ms message: 'network-check-target-ip-10-0-141-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:53:24Z" - latency: 2.387383ms message: 'network-check-target-ip-10-0-141-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:52:24Z" - latency: 2.256371ms message: 'network-check-target-ip-10-0-141-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:51:24Z" - latency: 2.026045ms message: 'network-check-target-ip-10-0-141-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:50:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T19:24:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-2-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-2.ec2.internal uid: b09549a5-dfef-4fd6-9506-82134d329109 resourceVersion: "57858" uid: af0c96b8-fee0-4632-9830-0e0e97fb9be6 spec: sourcePod: network-check-source-7bc5b6bf85-4lf8g targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-23T19:30:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 938.06µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T20:00:24Z" - latency: 1.73482ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T20:00:24Z" - latency: 783.705µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:59:24Z" - latency: 1.927401ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T19:59:24Z" - latency: 859.768µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:58:24Z" - latency: 1.507027ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T19:58:24Z" - latency: 718.082µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:57:24Z" - latency: 1.825771ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T19:57:24Z" - latency: 654.845µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:56:24Z" - latency: 1.836781ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T19:56:24Z" kind: List metadata: resourceVersion: ""