apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T00:11:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-68-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-68.ec2.internal uid: c298e23f-b008-4011-8f78-5ee85c443387 resourceVersion: "70065" uid: 9f04ead9-53ff-4316-b4a4-515b8d99b0bf spec: sourcePod: network-check-source-7d88cb55d8-l8j7b targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T00:18:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.047332ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:00:04Z" - latency: 915.67µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:59:04Z" - latency: 857.014µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:58:04Z" - latency: 1.632896ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:57:04Z" - latency: 1.159584ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:56:04Z" - latency: 786.96µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:55:04Z" - latency: 1.571684ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:54:04Z" - latency: 809.959µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:53:04Z" - latency: 832.126µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:52:04Z" - latency: 1.134243ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:51:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T00:11:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-68-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-68.ec2.internal uid: c298e23f-b008-4011-8f78-5ee85c443387 resourceVersion: "68765" uid: d6c80cb9-f9ef-4ed5-a9e7-f44adfe0a2d3 spec: sourcePod: network-check-source-7d88cb55d8-l8j7b targetEndpoint: abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T00:17:04Z" message: 'load-balancer-api-external: tcp connection to abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.132195ms message: 'load-balancer-api-external: tcp connection to abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:59:04Z" - latency: 9.713191ms message: 'load-balancer-api-external: resolved host name abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:59:04Z" - latency: 4.584914ms message: 'load-balancer-api-external: tcp connection to abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:58:04Z" - latency: 7.90579ms message: 'load-balancer-api-external: resolved host name abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:58:04Z" - latency: 4.4202ms message: 'load-balancer-api-external: tcp connection to abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:57:04Z" - latency: 13.177197ms message: 'load-balancer-api-external: resolved host name abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:57:04Z" - latency: 5.296019ms message: 'load-balancer-api-external: tcp connection to abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:56:04Z" - latency: 7.7444ms message: 'load-balancer-api-external: resolved host name abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:56:04Z" - latency: 4.411458ms message: 'load-balancer-api-external: tcp connection to abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:55:04Z" - latency: 7.570507ms message: 'load-balancer-api-external: resolved host name abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:55:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T00:11:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-68-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-68.ec2.internal uid: c298e23f-b008-4011-8f78-5ee85c443387 resourceVersion: "68766" uid: c057695d-4eb3-4cee-aa2f-8f293b19e76b spec: sourcePod: network-check-source-7d88cb55d8-l8j7b targetEndpoint: abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T00:17:04Z" message: 'load-balancer-api-internal: tcp connection to abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.122821ms message: 'load-balancer-api-internal: tcp connection to abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:59:04Z" - latency: 9.826336ms message: 'load-balancer-api-internal: resolved host name abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:59:04Z" - latency: 4.628863ms message: 'load-balancer-api-internal: tcp connection to abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:58:04Z" - latency: 7.941006ms message: 'load-balancer-api-internal: resolved host name abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:58:04Z" - latency: 5.07756ms message: 'load-balancer-api-internal: tcp connection to abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:57:04Z" - latency: 13.145038ms message: 'load-balancer-api-internal: resolved host name abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:57:04Z" - latency: 4.061284ms message: 'load-balancer-api-internal: tcp connection to abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:56:04Z" - latency: 7.556734ms message: 'load-balancer-api-internal: resolved host name abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:56:04Z" - latency: 4.380211ms message: 'load-balancer-api-internal: tcp connection to abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:55:04Z" - latency: 7.486002ms message: 'load-balancer-api-internal: resolved host name abce23444255c4b7aa36456d28d7f21f-aec9aecf042dcbcf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:55:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T00:11:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-68-to-network-check-target-ip-10-0-131-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-68.ec2.internal uid: c298e23f-b008-4011-8f78-5ee85c443387 resourceVersion: "70062" uid: ac4eb767-e6e3-44d0-b837-beafef35c22e spec: sourcePod: network-check-source-7d88cb55d8-l8j7b targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T00:18:04Z" message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 978.726µs message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:00:04Z" - latency: 1.13379ms message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:59:04Z" - latency: 856.719µs message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:58:04Z" - latency: 1.021216ms message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:57:04Z" - latency: 1.610926ms message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:56:04Z" - latency: 804.943µs message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:55:04Z" - latency: 931.277µs message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:54:04Z" - latency: 1.125266ms message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:53:04Z" - latency: 1.74483ms message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:52:04Z" - latency: 1.163667ms message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:51:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T00:11:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-68-to-network-check-target-ip-10-0-133-130 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-68.ec2.internal uid: c298e23f-b008-4011-8f78-5ee85c443387 resourceVersion: "70063" uid: a898ab32-91bb-4a6a-b75d-f15e33c0fc75 spec: sourcePod: network-check-source-7d88cb55d8-l8j7b targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T00:18:04Z" message: 'network-check-target-ip-10-0-133-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.353021ms message: 'network-check-target-ip-10-0-133-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:00:04Z" - latency: 2.338843ms message: 'network-check-target-ip-10-0-133-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:59:04Z" - latency: 1.794724ms message: 'network-check-target-ip-10-0-133-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:58:04Z" - latency: 2.403215ms message: 'network-check-target-ip-10-0-133-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:57:04Z" - latency: 2.481684ms message: 'network-check-target-ip-10-0-133-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:56:04Z" - latency: 2.224707ms message: 'network-check-target-ip-10-0-133-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:55:04Z" - latency: 2.254664ms message: 'network-check-target-ip-10-0-133-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:54:04Z" - latency: 1.986524ms message: 'network-check-target-ip-10-0-133-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:53:04Z" - latency: 2.459172ms message: 'network-check-target-ip-10-0-133-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:52:04Z" - latency: 2.900464ms message: 'network-check-target-ip-10-0-133-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:51:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T00:11:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-68-to-network-check-target-ip-10-0-139-127 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-68.ec2.internal uid: c298e23f-b008-4011-8f78-5ee85c443387 resourceVersion: "70064" uid: a1103407-b3a9-4327-bbae-3ea154710b6b spec: sourcePod: network-check-source-7d88cb55d8-l8j7b targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T00:18:04Z" message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.251519ms message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:00:04Z" - latency: 2.484565ms message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:59:04Z" - latency: 1.85338ms message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:58:04Z" - latency: 2.517843ms message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:57:04Z" - latency: 2.414053ms message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:56:04Z" - latency: 1.692015ms message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:55:04Z" - latency: 2.54622ms message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:54:04Z" - latency: 1.924321ms message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:53:04Z" - latency: 2.503106ms message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:52:04Z" - latency: 2.425716ms message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:51:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T00:11:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-68-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-68.ec2.internal uid: c298e23f-b008-4011-8f78-5ee85c443387 resourceVersion: "68764" uid: 11849d8f-8ba7-46b3-95fa-49c51e6aaed5 spec: sourcePod: network-check-source-7d88cb55d8-l8j7b targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T00:17:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.049117ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:59:04Z" - latency: 1.74941ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T00:59:04Z" - latency: 971.95µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:58:04Z" - latency: 1.766851ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T00:58:04Z" - latency: 894.94µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:57:04Z" - latency: 1.820819ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T00:57:04Z" - latency: 1.005472ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:56:04Z" - latency: 1.858566ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T00:56:04Z" - latency: 932.684µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:55:04Z" - latency: 1.702034ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T00:55:04Z" kind: List metadata: resourceVersion: ""