apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T00:24:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-219-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-219.ec2.internal uid: a83cbe64-092a-4422-9bcf-cfe2c6352208 resourceVersion: "30775" uid: c8f1b55b-5e25-44f1-bbaf-5dbfc085b909 spec: sourcePod: network-check-source-56d84b9f44-zmjh5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-03T00:31:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.070586ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:38:29Z" - latency: 1.56314ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:37:29Z" - latency: 791.438µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:36:29Z" - latency: 808.788µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:35:29Z" - latency: 798.502µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:34:29Z" - latency: 1.260539ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:33:29Z" - latency: 1.235522ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:32:29Z" - latency: 820.844µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:31:29Z" - latency: 1.229087ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:30:29Z" - latency: 953.452µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:29:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T00:24:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-219-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-219.ec2.internal uid: a83cbe64-092a-4422-9bcf-cfe2c6352208 resourceVersion: "29243" uid: 61092184-cfae-4596-be6a-88fefe264b71 spec: sourcePod: network-check-source-56d84b9f44-zmjh5 targetEndpoint: a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T00:30:29Z" message: 'load-balancer-api-external: tcp connection to a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.526496ms message: 'load-balancer-api-external: tcp connection to a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:36:29Z" - latency: 6.477601ms message: 'load-balancer-api-external: resolved host name a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T00:36:29Z" - latency: 7.818674ms message: 'load-balancer-api-external: tcp connection to a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:35:29Z" - latency: 6.960122ms message: 'load-balancer-api-external: resolved host name a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T00:35:29Z" - latency: 3.968ms message: 'load-balancer-api-external: tcp connection to a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:34:29Z" - latency: 7.657863ms message: 'load-balancer-api-external: resolved host name a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T00:34:29Z" - latency: 5.167624ms message: 'load-balancer-api-external: tcp connection to a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:33:29Z" - latency: 7.700446ms message: 'load-balancer-api-external: resolved host name a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T00:33:29Z" - latency: 5.414141ms message: 'load-balancer-api-external: tcp connection to a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:32:29Z" - latency: 7.110525ms message: 'load-balancer-api-external: resolved host name a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T00:32:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T00:24:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-219-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-219.ec2.internal uid: a83cbe64-092a-4422-9bcf-cfe2c6352208 resourceVersion: "29242" uid: 783f7205-0a91-4d6f-9fd6-52333409862f spec: sourcePod: network-check-source-56d84b9f44-zmjh5 targetEndpoint: a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T00:30:29Z" message: 'load-balancer-api-internal: tcp connection to a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.268352ms message: 'load-balancer-api-internal: tcp connection to a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:36:29Z" - latency: 6.463273ms message: 'load-balancer-api-internal: resolved host name a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T00:36:29Z" - latency: 7.809484ms message: 'load-balancer-api-internal: tcp connection to a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:35:29Z" - latency: 6.924327ms message: 'load-balancer-api-internal: resolved host name a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T00:35:29Z" - latency: 3.919583ms message: 'load-balancer-api-internal: tcp connection to a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:34:29Z" - latency: 7.575197ms message: 'load-balancer-api-internal: resolved host name a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T00:34:29Z" - latency: 4.587085ms message: 'load-balancer-api-internal: tcp connection to a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:33:29Z" - latency: 6.927454ms message: 'load-balancer-api-internal: resolved host name a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T00:33:29Z" - latency: 4.747411ms message: 'load-balancer-api-internal: tcp connection to a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:32:29Z" - latency: 7.086441ms message: 'load-balancer-api-internal: resolved host name a521c6e4d762b42b39ecbbac9eec16a5-714588ebb2973587.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T00:32:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T00:24:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-219-to-network-check-target-ip-10-0-129-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-219.ec2.internal uid: a83cbe64-092a-4422-9bcf-cfe2c6352208 resourceVersion: "30773" uid: 11f3eacf-517e-4a4d-be17-cdb7f68547e9 spec: sourcePod: network-check-source-56d84b9f44-zmjh5 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-03T00:31:29Z" message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.058027ms message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:38:29Z" - latency: 2.236481ms message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:37:29Z" - latency: 2.17912ms message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:36:29Z" - latency: 1.987628ms message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:35:29Z" - latency: 2.354566ms message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:34:29Z" - latency: 2.533533ms message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:33:29Z" - latency: 2.221152ms message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:32:29Z" - latency: 1.994262ms message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:31:29Z" - latency: 2.306136ms message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:30:29Z" - latency: 2.010835ms message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:29:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T00:24:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-219-to-network-check-target-ip-10-0-130-219 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-219.ec2.internal uid: a83cbe64-092a-4422-9bcf-cfe2c6352208 resourceVersion: "30772" uid: ab24e067-e5ee-48fa-895c-d0c6b42ef5f2 spec: sourcePod: network-check-source-56d84b9f44-zmjh5 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-03T00:31:29Z" message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 875.103µs message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:38:29Z" - latency: 1.172732ms message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:37:29Z" - latency: 932.315µs message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:36:29Z" - latency: 954.762µs message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:35:29Z" - latency: 1.009074ms message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:34:29Z" - latency: 1.797202ms message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:33:29Z" - latency: 794.538µs message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:32:29Z" - latency: 896.604µs message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:31:29Z" - latency: 972.352µs message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:30:29Z" - latency: 942.348µs message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:29:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T00:24:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-219-to-network-check-target-ip-10-0-135-206 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-219.ec2.internal uid: a83cbe64-092a-4422-9bcf-cfe2c6352208 resourceVersion: "30774" uid: 25610906-3f18-40fe-93f9-6fcd2715b13f spec: sourcePod: network-check-source-56d84b9f44-zmjh5 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-03T00:31:29Z" message: 'network-check-target-ip-10-0-135-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.183641ms message: 'network-check-target-ip-10-0-135-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:38:29Z" - latency: 2.243492ms message: 'network-check-target-ip-10-0-135-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:37:29Z" - latency: 2.002938ms message: 'network-check-target-ip-10-0-135-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:36:29Z" - latency: 2.11533ms message: 'network-check-target-ip-10-0-135-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:35:29Z" - latency: 2.219149ms message: 'network-check-target-ip-10-0-135-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:34:29Z" - latency: 2.502404ms message: 'network-check-target-ip-10-0-135-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:33:29Z" - latency: 2.673378ms message: 'network-check-target-ip-10-0-135-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:32:29Z" - latency: 1.974415ms message: 'network-check-target-ip-10-0-135-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:31:29Z" - latency: 2.392011ms message: 'network-check-target-ip-10-0-135-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:30:29Z" - latency: 2.525324ms message: 'network-check-target-ip-10-0-135-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:29:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T00:24:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-219-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-219.ec2.internal uid: a83cbe64-092a-4422-9bcf-cfe2c6352208 resourceVersion: "29241" uid: f38266c0-ddfa-4f53-9378-6ff2ffd9a63c spec: sourcePod: network-check-source-56d84b9f44-zmjh5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-03T00:30:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.319µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:36:29Z" - latency: 1.589729ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T00:36:29Z" - latency: 1.270192ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:35:29Z" - latency: 1.622655ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T00:35:29Z" - latency: 747.33µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:34:29Z" - latency: 1.717805ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T00:34:29Z" - latency: 1.167895ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:33:29Z" - latency: 2.661999ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T00:33:29Z" - latency: 836.993µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T00:32:29Z" - latency: 1.828609ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T00:32:29Z" kind: List metadata: resourceVersion: ""