apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:59:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-112-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-112.ec2.internal uid: c6b67cff-da0c-4c70-86a0-3ab3d99e7ef7 resourceVersion: "38375" uid: 89774971-abab-4d24-a0b2-4ac53c691ac6 spec: sourcePod: network-check-source-8894fc9bd-vpl9w targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T18:06:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.013862ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:02:51Z" - latency: 912.881µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:01:51Z" - latency: 760.676µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:00:51Z" - latency: 1.147656ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:59:51Z" - latency: 1.177833ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:58:51Z" - latency: 957.835µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:57:51Z" - latency: 757.311µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:56:51Z" - latency: 1.047347ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:55:51Z" - latency: 1.33266ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:54:51Z" - latency: 952.487µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:53:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:59:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-112-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-112.ec2.internal uid: c6b67cff-da0c-4c70-86a0-3ab3d99e7ef7 resourceVersion: "36886" uid: 457220d3-2c88-41b1-a9d2-edb65343946c spec: sourcePod: network-check-source-8894fc9bd-vpl9w targetEndpoint: a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T18:05:51Z" message: 'load-balancer-api-external: tcp connection to a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.699505ms message: 'load-balancer-api-external: tcp connection to a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:59:51Z" - latency: 10.038381ms message: 'load-balancer-api-external: resolved host name a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:59:51Z" - latency: 3.970877ms message: 'load-balancer-api-external: tcp connection to a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:58:51Z" - latency: 10.610931ms message: 'load-balancer-api-external: resolved host name a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:58:51Z" - latency: 4.439131ms message: 'load-balancer-api-external: tcp connection to a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:57:51Z" - latency: 10.605496ms message: 'load-balancer-api-external: resolved host name a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:57:51Z" - latency: 4.766067ms message: 'load-balancer-api-external: tcp connection to a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:56:51Z" - latency: 11.609171ms message: 'load-balancer-api-external: resolved host name a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:56:51Z" - latency: 6.024878ms message: 'load-balancer-api-external: tcp connection to a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:55:51Z" - latency: 10.370099ms message: 'load-balancer-api-external: resolved host name a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:55:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:59:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-112-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-112.ec2.internal uid: c6b67cff-da0c-4c70-86a0-3ab3d99e7ef7 resourceVersion: "36887" uid: df2c4ada-d81c-4c9a-aa43-eb00b5f8c51a spec: sourcePod: network-check-source-8894fc9bd-vpl9w targetEndpoint: a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T18:05:51Z" message: 'load-balancer-api-internal: tcp connection to a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.119267ms message: 'load-balancer-api-internal: tcp connection to a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:59:51Z" - latency: 10.011715ms message: 'load-balancer-api-internal: resolved host name a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:59:51Z" - latency: 4.407795ms message: 'load-balancer-api-internal: tcp connection to a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:58:51Z" - latency: 10.557668ms message: 'load-balancer-api-internal: resolved host name a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:58:51Z" - latency: 4.461474ms message: 'load-balancer-api-internal: tcp connection to a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:57:51Z" - latency: 10.637511ms message: 'load-balancer-api-internal: resolved host name a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:57:51Z" - latency: 4.978893ms message: 'load-balancer-api-internal: tcp connection to a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:56:51Z" - latency: 11.471674ms message: 'load-balancer-api-internal: resolved host name a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:56:51Z" - latency: 6.034352ms message: 'load-balancer-api-internal: tcp connection to a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:55:51Z" - latency: 10.345588ms message: 'load-balancer-api-internal: resolved host name a422dbee3ef56468a9239c0d3b89ff56-a52af8bcb005d4b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:55:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:59:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-112-to-network-check-target-ip-10-0-130-112 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-112.ec2.internal uid: c6b67cff-da0c-4c70-86a0-3ab3d99e7ef7 resourceVersion: "38372" uid: 2f9b707b-020f-48b8-a36f-a4a4e76aac8c spec: sourcePod: network-check-source-8894fc9bd-vpl9w targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:06:51Z" message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 891.677µs message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:02:51Z" - latency: 1.293157ms message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:01:51Z" - latency: 920.508µs message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:00:51Z" - latency: 810.106µs message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:59:51Z" - latency: 888.495µs message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:58:51Z" - latency: 888.807µs message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:57:51Z" - latency: 854.846µs message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:56:51Z" - latency: 794.886µs message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:55:51Z" - latency: 1.210332ms message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:54:51Z" - latency: 971.572µs message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:53:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:59:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-112-to-network-check-target-ip-10-0-135-21 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-112.ec2.internal uid: c6b67cff-da0c-4c70-86a0-3ab3d99e7ef7 resourceVersion: "38374" uid: c7ea3db9-0a36-462f-94bb-de1d73983534 spec: sourcePod: network-check-source-8894fc9bd-vpl9w targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:06:51Z" message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.145598ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:02:51Z" - latency: 2.072027ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:01:51Z" - latency: 2.283145ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:00:51Z" - latency: 2.09685ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:59:51Z" - latency: 2.198936ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:58:51Z" - latency: 2.192537ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:57:51Z" - latency: 2.124537ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:56:51Z" - latency: 2.146699ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:55:51Z" - latency: 2.249439ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:54:51Z" - latency: 2.159876ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:53:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:59:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-112-to-network-check-target-ip-10-0-143-11 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-112.ec2.internal uid: c6b67cff-da0c-4c70-86a0-3ab3d99e7ef7 resourceVersion: "38373" uid: 7d386494-d82a-4034-be58-644c9964346e spec: sourcePod: network-check-source-8894fc9bd-vpl9w targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:06:51Z" message: 'network-check-target-ip-10-0-143-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.944675ms message: 'network-check-target-ip-10-0-143-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:02:51Z" - latency: 1.768394ms message: 'network-check-target-ip-10-0-143-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:01:51Z" - latency: 1.559886ms message: 'network-check-target-ip-10-0-143-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:00:51Z" - latency: 1.89065ms message: 'network-check-target-ip-10-0-143-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:59:51Z" - latency: 1.868753ms message: 'network-check-target-ip-10-0-143-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:58:51Z" - latency: 1.914343ms message: 'network-check-target-ip-10-0-143-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:57:51Z" - latency: 1.939116ms message: 'network-check-target-ip-10-0-143-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:56:51Z" - latency: 1.740255ms message: 'network-check-target-ip-10-0-143-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:55:51Z" - latency: 1.837002ms message: 'network-check-target-ip-10-0-143-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:54:51Z" - latency: 1.789516ms message: 'network-check-target-ip-10-0-143-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:53:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:59:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-112-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-112.ec2.internal uid: c6b67cff-da0c-4c70-86a0-3ab3d99e7ef7 resourceVersion: "36885" uid: 7fa9fbc6-73ad-49c1-928a-4cc035d0b1da spec: sourcePod: network-check-source-8894fc9bd-vpl9w targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T18:05:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 768.899µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:59:51Z" - latency: 1.595136ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T18:59:51Z" - latency: 903.812µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:58:51Z" - latency: 1.739305ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T18:58:51Z" - latency: 1.071109ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:57:51Z" - latency: 1.643436ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T18:57:51Z" - latency: 771.606µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:56:51Z" - latency: 1.902027ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T18:56:51Z" - latency: 994.4µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:55:51Z" - latency: 1.692045ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T18:55:51Z" kind: List metadata: resourceVersion: ""