apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T11:42:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-199-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-199.ec2.internal uid: ec5be049-30d1-410e-afeb-1c40ec2f0493 resourceVersion: "45006" uid: 2528606a-ce3e-44a7-a74b-c6b787da906e spec: sourcePod: network-check-source-dbd9cf844-wztvc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-10T11:49:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 873.968µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:10:19Z" - latency: 942.418µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:09:19Z" - latency: 1.416964ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:08:19Z" - latency: 1.146469ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:07:19Z" - latency: 863.243µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:06:19Z" - latency: 839.74µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:05:19Z" - latency: 1.293225ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:04:19Z" - latency: 1.060065ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:03:19Z" - latency: 827.913µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:02:19Z" - latency: 1.122106ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:01:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T11:42:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-199-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-199.ec2.internal uid: ec5be049-30d1-410e-afeb-1c40ec2f0493 resourceVersion: "46919" uid: b148c1a0-a060-4f4d-b608-d63485c77641 spec: sourcePod: network-check-source-dbd9cf844-wztvc targetEndpoint: ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T11:48:19Z" message: 'load-balancer-api-external: tcp connection to ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.944548ms message: 'load-balancer-api-external: tcp connection to ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:12:19Z" - latency: 8.743529ms message: 'load-balancer-api-external: resolved host name ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:12:19Z" - latency: 4.972367ms message: 'load-balancer-api-external: tcp connection to ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:11:19Z" - latency: 10.00383ms message: 'load-balancer-api-external: resolved host name ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:11:19Z" - latency: 3.992546ms message: 'load-balancer-api-external: tcp connection to ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:10:19Z" - latency: 8.694907ms message: 'load-balancer-api-external: resolved host name ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:10:19Z" - latency: 4.633179ms message: 'load-balancer-api-external: tcp connection to ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:09:19Z" - latency: 9.150275ms message: 'load-balancer-api-external: resolved host name ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:09:19Z" - latency: 4.813568ms message: 'load-balancer-api-external: tcp connection to ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:08:19Z" - latency: 8.37786ms message: 'load-balancer-api-external: resolved host name ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:08:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T11:42:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-199-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-199.ec2.internal uid: ec5be049-30d1-410e-afeb-1c40ec2f0493 resourceVersion: "46920" uid: 72e021f0-21b2-414a-a6e5-8abe2c6250df spec: sourcePod: network-check-source-dbd9cf844-wztvc targetEndpoint: ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T11:48:19Z" message: 'load-balancer-api-internal: tcp connection to ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.546751ms message: 'load-balancer-api-internal: tcp connection to ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:12:19Z" - latency: 8.698538ms message: 'load-balancer-api-internal: resolved host name ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:12:19Z" - latency: 4.275484ms message: 'load-balancer-api-internal: tcp connection to ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:11:19Z" - latency: 9.983794ms message: 'load-balancer-api-internal: resolved host name ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:11:19Z" - latency: 3.97499ms message: 'load-balancer-api-internal: tcp connection to ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:10:19Z" - latency: 8.590996ms message: 'load-balancer-api-internal: resolved host name ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:10:19Z" - latency: 5.906494ms message: 'load-balancer-api-internal: tcp connection to ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:09:19Z" - latency: 9.126567ms message: 'load-balancer-api-internal: resolved host name ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:09:19Z" - latency: 4.463824ms message: 'load-balancer-api-internal: tcp connection to ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:08:19Z" - latency: 8.307694ms message: 'load-balancer-api-internal: resolved host name ac9f510f0c1ef471a80304f42ae1de67-477bdb8260bc2513.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:08:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T11:42:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-199-to-network-check-target-ip-10-0-132-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-199.ec2.internal uid: ec5be049-30d1-410e-afeb-1c40ec2f0493 resourceVersion: "45005" uid: 4f83d04b-e2c5-4c0f-868b-e5787e6cc076 spec: sourcePod: network-check-source-dbd9cf844-wztvc targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-10T11:49:19Z" message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.138969ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:10:19Z" - latency: 2.212684ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:09:19Z" - latency: 2.251955ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:08:19Z" - latency: 2.061193ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:07:19Z" - latency: 1.813937ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:06:19Z" - latency: 1.986627ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:05:19Z" - latency: 2.351113ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:04:19Z" - latency: 2.068328ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:03:19Z" - latency: 1.666277ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:02:19Z" - latency: 1.938261ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:01:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T11:42:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-199-to-network-check-target-ip-10-0-134-56 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-199.ec2.internal uid: ec5be049-30d1-410e-afeb-1c40ec2f0493 resourceVersion: "45004" uid: 951d35dc-8674-4429-aff2-7436471bbbe7 spec: sourcePod: network-check-source-dbd9cf844-wztvc targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T11:49:19Z" message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.800604ms message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:10:19Z" - latency: 2.050332ms message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:09:19Z" - latency: 1.908038ms message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:08:19Z" - latency: 1.540307ms message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:07:19Z" - latency: 1.85903ms message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:06:19Z" - latency: 1.784658ms message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:05:19Z" - latency: 2.716889ms message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:04:19Z" - latency: 2.071273ms message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:03:19Z" - latency: 1.721874ms message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:02:19Z" - latency: 1.380939ms message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:01:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T11:42:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-199-to-network-check-target-ip-10-0-142-199 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-199.ec2.internal uid: ec5be049-30d1-410e-afeb-1c40ec2f0493 resourceVersion: "45003" uid: b3df5821-66e1-4b2d-9425-8b03a373cb76 spec: sourcePod: network-check-source-dbd9cf844-wztvc targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-10T11:49:19Z" message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 767.528µs message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:10:19Z" - latency: 997.915µs message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:09:19Z" - latency: 820.526µs message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:08:19Z" - latency: 870.289µs message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:07:19Z" - latency: 1.030005ms message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:06:19Z" - latency: 1.396522ms message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:05:19Z" - latency: 1.185052ms message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:04:19Z" - latency: 855.382µs message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:03:19Z" - latency: 842.945µs message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:02:19Z" - latency: 785.689µs message: 'network-check-target-ip-10-0-142-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:01:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T11:42:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-199-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-199.ec2.internal uid: ec5be049-30d1-410e-afeb-1c40ec2f0493 resourceVersion: "46918" uid: 145f8b1e-e6ac-46b6-bb58-a1f8f9bcc972 spec: sourcePod: network-check-source-dbd9cf844-wztvc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-10T11:48:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 911.775µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:12:19Z" - latency: 1.686693ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:12:19Z" - latency: 994.319µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:11:19Z" - latency: 2.032813ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:11:19Z" - latency: 823.318µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:10:19Z" - latency: 1.724085ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:10:19Z" - latency: 1.166523ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:09:19Z" - latency: 1.790903ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:09:19Z" - latency: 1.149887ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:08:19Z" - latency: 1.737057ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:08:19Z" kind: List metadata: resourceVersion: ""