apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:19:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-16-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-16.ec2.internal uid: be626588-021b-4301-ad86-5d525238eebd resourceVersion: "34044" uid: 4f0f66a4-2651-42d0-98a0-ac9220ace603 spec: sourcePod: network-check-source-8894fc9bd-8m6vz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T22:26:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 790.715µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:40:04Z" - latency: 978.134µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:39:04Z" - latency: 965.442µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:38:04Z" - latency: 1.86363ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:37:04Z" - latency: 1.149313ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:36:04Z" - latency: 1.707973ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:35:04Z" - latency: 1.347311ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:34:04Z" - latency: 1.300792ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:33:04Z" - latency: 804.962µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:32:04Z" - latency: 1.097979ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:31:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:19:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-16-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-16.ec2.internal uid: be626588-021b-4301-ad86-5d525238eebd resourceVersion: "31175" uid: 3a7cd624-f5b7-4c0e-8637-8df56779d7db spec: sourcePod: network-check-source-8894fc9bd-8m6vz targetEndpoint: a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T22:25:04Z" message: 'load-balancer-api-external: tcp connection to a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.207228ms message: 'load-balancer-api-external: tcp connection to a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:37:04Z" - latency: 7.970287ms message: 'load-balancer-api-external: resolved host name a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:37:04Z" - latency: 4.430745ms message: 'load-balancer-api-external: tcp connection to a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:36:04Z" - latency: 7.598488ms message: 'load-balancer-api-external: resolved host name a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:36:04Z" - latency: 9.497464ms message: 'load-balancer-api-external: tcp connection to a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:35:04Z" - latency: 10.325326ms message: 'load-balancer-api-external: resolved host name a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:35:04Z" - latency: 4.462469ms message: 'load-balancer-api-external: tcp connection to a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:34:04Z" - latency: 8.094251ms message: 'load-balancer-api-external: resolved host name a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:34:04Z" - latency: 4.220801ms message: 'load-balancer-api-external: tcp connection to a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:33:04Z" - latency: 6.625544ms message: 'load-balancer-api-external: resolved host name a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:33:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:19:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-16-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-16.ec2.internal uid: be626588-021b-4301-ad86-5d525238eebd resourceVersion: "31174" uid: 721100f9-368c-4921-a7b1-cf472894ad17 spec: sourcePod: network-check-source-8894fc9bd-8m6vz targetEndpoint: a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T22:25:04Z" message: 'load-balancer-api-internal: tcp connection to a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.189095ms message: 'load-balancer-api-internal: tcp connection to a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:37:04Z" - latency: 8.041733ms message: 'load-balancer-api-internal: resolved host name a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:37:04Z" - latency: 4.398653ms message: 'load-balancer-api-internal: tcp connection to a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:36:04Z" - latency: 7.671823ms message: 'load-balancer-api-internal: resolved host name a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:36:04Z" - latency: 5.08276ms message: 'load-balancer-api-internal: tcp connection to a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:35:04Z" - latency: 10.407944ms message: 'load-balancer-api-internal: resolved host name a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:35:04Z" - latency: 5.130817ms message: 'load-balancer-api-internal: tcp connection to a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:34:04Z" - latency: 8.124655ms message: 'load-balancer-api-internal: resolved host name a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:34:04Z" - latency: 5.825943ms message: 'load-balancer-api-internal: tcp connection to a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:33:04Z" - latency: 6.821236ms message: 'load-balancer-api-internal: resolved host name a67a2be3ab8a24121bf215289b85aa5e-c8c4b92e86c84c51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:33:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:19:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-16-to-network-check-target-ip-10-0-133-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-16.ec2.internal uid: be626588-021b-4301-ad86-5d525238eebd resourceVersion: "34041" uid: 40a0b1c4-a4d3-4dbb-8aa8-2d1306e00f38 spec: sourcePod: network-check-source-8894fc9bd-8m6vz targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T22:26:04Z" message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.086764ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:40:04Z" - latency: 1.140072ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:39:04Z" - latency: 796.745µs message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:38:04Z" - latency: 1.436306ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:37:04Z" - latency: 1.276095ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:36:04Z" - latency: 1.437992ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:35:04Z" - latency: 1.049558ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:34:04Z" - latency: 1.204744ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:33:04Z" - latency: 1.28777ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:32:04Z" - latency: 1.066547ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:31:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:19:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-16-to-network-check-target-ip-10-0-133-72 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-16.ec2.internal uid: be626588-021b-4301-ad86-5d525238eebd resourceVersion: "34042" uid: 6cde685c-478b-49a8-ae48-41177a7dec85 spec: sourcePod: network-check-source-8894fc9bd-8m6vz targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-16T22:26:04Z" message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.300047ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:40:04Z" - latency: 2.073041ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:39:04Z" - latency: 1.892743ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:38:04Z" - latency: 2.23626ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:37:04Z" - latency: 1.664353ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:36:04Z" - latency: 1.968495ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:35:04Z" - latency: 1.728441ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:34:04Z" - latency: 1.967277ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:33:04Z" - latency: 1.656479ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:32:04Z" - latency: 1.969713ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:31:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:19:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-16-to-network-check-target-ip-10-0-135-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-16.ec2.internal uid: be626588-021b-4301-ad86-5d525238eebd resourceVersion: "34043" uid: 4fa61975-2350-4995-8bc8-df20faff552f spec: sourcePod: network-check-source-8894fc9bd-8m6vz targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T22:26:04Z" message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.159265ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:40:04Z" - latency: 2.325538ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:39:04Z" - latency: 2.497228ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:38:04Z" - latency: 3.340761ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:37:04Z" - latency: 2.258662ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:36:04Z" - latency: 2.251452ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:35:04Z" - latency: 2.112791ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:34:04Z" - latency: 2.322743ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:33:04Z" - latency: 2.172743ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:32:04Z" - latency: 2.387483ms message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:31:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:19:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-16-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-16.ec2.internal uid: be626588-021b-4301-ad86-5d525238eebd resourceVersion: "31173" uid: e47011f0-0993-4006-af6a-c544b95d81e0 spec: sourcePod: network-check-source-8894fc9bd-8m6vz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T22:25:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 824.376µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:37:04Z" - latency: 2.490033ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T22:37:04Z" - latency: 727.878µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:36:04Z" - latency: 1.819287ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T22:36:04Z" - latency: 873.983µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:35:04Z" - latency: 1.720129ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T22:35:04Z" - latency: 713.921µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:34:04Z" - latency: 1.683762ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T22:34:04Z" - latency: 1.113758ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:33:04Z" - latency: 1.792632ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T22:33:04Z" kind: List metadata: resourceVersion: ""