apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T19:26:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: a002fad3-fd1a-445a-a4db-754b7eba3771 resourceVersion: "43849" uid: 56cbf9bf-ea8d-43bd-a3ca-5c54785c0e44 spec: sourcePod: network-check-source-8894fc9bd-rtw9q targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-20T19:33:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 892.245µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:54:17Z" - latency: 789.721µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:53:17Z" - latency: 1.075159ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:52:17Z" - latency: 1.016005ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:51:17Z" - latency: 1.504711ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:50:17Z" - latency: 681.14µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:49:17Z" - latency: 1.364964ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:48:17Z" - latency: 1.188432ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:47:17Z" - latency: 976.675µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:46:17Z" - latency: 1.199413ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:45:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T19:26:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: a002fad3-fd1a-445a-a4db-754b7eba3771 resourceVersion: "46106" uid: c4bc7980-288e-4358-a118-5adda05d7a55 spec: sourcePod: network-check-source-8894fc9bd-rtw9q targetEndpoint: a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T19:32:17Z" message: 'load-balancer-api-external: tcp connection to a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.381672ms message: 'load-balancer-api-external: tcp connection to a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:56:17Z" - latency: 7.560782ms message: 'load-balancer-api-external: resolved host name a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:56:17Z" - latency: 5.128131ms message: 'load-balancer-api-external: tcp connection to a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:55:17Z" - latency: 7.202983ms message: 'load-balancer-api-external: resolved host name a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:55:17Z" - latency: 4.984316ms message: 'load-balancer-api-external: tcp connection to a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:54:17Z" - latency: 7.649418ms message: 'load-balancer-api-external: resolved host name a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:54:17Z" - latency: 5.023469ms message: 'load-balancer-api-external: tcp connection to a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:53:17Z" - latency: 7.067697ms message: 'load-balancer-api-external: resolved host name a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:53:17Z" - latency: 3.193426ms message: 'load-balancer-api-external: tcp connection to a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:52:17Z" - latency: 6.167526ms message: 'load-balancer-api-external: resolved host name a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:52:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T19:26:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: a002fad3-fd1a-445a-a4db-754b7eba3771 resourceVersion: "46107" uid: 526dbec2-d54e-4b86-979d-56e7c6b03257 spec: sourcePod: network-check-source-8894fc9bd-rtw9q targetEndpoint: a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T19:32:17Z" message: 'load-balancer-api-internal: tcp connection to a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.745114ms message: 'load-balancer-api-internal: tcp connection to a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:56:17Z" - latency: 7.518013ms message: 'load-balancer-api-internal: resolved host name a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:56:17Z" - latency: 5.146601ms message: 'load-balancer-api-internal: tcp connection to a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:55:17Z" - latency: 7.190713ms message: 'load-balancer-api-internal: resolved host name a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:55:17Z" - latency: 4.965481ms message: 'load-balancer-api-internal: tcp connection to a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:54:17Z" - latency: 7.55059ms message: 'load-balancer-api-internal: resolved host name a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:54:17Z" - latency: 5.036696ms message: 'load-balancer-api-internal: tcp connection to a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:53:17Z" - latency: 7.053185ms message: 'load-balancer-api-internal: resolved host name a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:53:17Z" - latency: 4.265972ms message: 'load-balancer-api-internal: tcp connection to a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:52:17Z" - latency: 6.271387ms message: 'load-balancer-api-internal: resolved host name a10337076370543cd96e7e868acdd6a4-a02bff750de4ba84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:52:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T19:26:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-network-check-target-ip-10-0-129-98 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: a002fad3-fd1a-445a-a4db-754b7eba3771 resourceVersion: "43848" uid: 6b681c6b-da6b-43f3-9897-390c17fa4396 spec: sourcePod: network-check-source-8894fc9bd-rtw9q targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-20T19:33:17Z" message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.167102ms message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:54:17Z" - latency: 2.213829ms message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:53:17Z" - latency: 2.245777ms message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:52:17Z" - latency: 2.368757ms message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:51:17Z" - latency: 2.603781ms message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:50:17Z" - latency: 2.092655ms message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:49:17Z" - latency: 2.187304ms message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:48:17Z" - latency: 2.310805ms message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:47:17Z" - latency: 2.350064ms message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:46:17Z" - latency: 2.54738ms message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:45:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T19:26:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-network-check-target-ip-10-0-133-149 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: a002fad3-fd1a-445a-a4db-754b7eba3771 resourceVersion: "43847" uid: 58e7366a-8a18-4152-bbac-13296a3a808b spec: sourcePod: network-check-source-8894fc9bd-rtw9q targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-20T19:33:17Z" message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.225071ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:54:17Z" - latency: 2.286146ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:53:17Z" - latency: 2.29896ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:52:17Z" - latency: 2.425561ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:51:17Z" - latency: 2.131901ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:50:17Z" - latency: 1.717719ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:49:17Z" - latency: 2.213371ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:48:17Z" - latency: 2.304277ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:47:17Z" - latency: 2.528691ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:46:17Z" - latency: 2.21704ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:45:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T19:26:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-network-check-target-ip-10-0-134-118 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: a002fad3-fd1a-445a-a4db-754b7eba3771 resourceVersion: "43846" uid: f9db8d4e-b6fe-47ef-95ff-8ae9a68a3292 spec: sourcePod: network-check-source-8894fc9bd-rtw9q targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-20T19:33:17Z" message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 932.336µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:54:17Z" - latency: 883.802µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:53:17Z" - latency: 1.047774ms message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:52:17Z" - latency: 872.998µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:51:17Z" - latency: 873.905µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:50:17Z" - latency: 1.071576ms message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:49:17Z" - latency: 1.058276ms message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:48:17Z" - latency: 1.018376ms message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:47:17Z" - latency: 1.242152ms message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:46:17Z" - latency: 958.075µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:45:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T19:26:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: a002fad3-fd1a-445a-a4db-754b7eba3771 resourceVersion: "46105" uid: bbaf6946-7ee6-4d5c-8744-0357bc6a1af9 spec: sourcePod: network-check-source-8894fc9bd-rtw9q targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-20T19:32:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 780.736µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:56:17Z" - latency: 2.351155ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T19:56:17Z" - latency: 845.932µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:55:17Z" - latency: 2.372123ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T19:55:17Z" - latency: 949.296µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:54:17Z" - latency: 1.761855ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T19:54:17Z" - latency: 1.187082ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:53:17Z" - latency: 1.923488ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T19:53:17Z" - latency: 1.364615ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:52:17Z" - latency: 1.609824ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T19:52:17Z" kind: List metadata: resourceVersion: ""