apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T04:27:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-81-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-81.ec2.internal uid: 29e27961-be7f-4bb1-a5da-4de596c531e1 resourceVersion: "37384" uid: a73a695e-9516-4799-bacb-25edc899e738 spec: sourcePod: network-check-source-7b678d77c7-qnjs2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T04:34:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.178552ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:48:54Z" - latency: 831.174µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:47:54Z" - latency: 1.003429ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:46:54Z" - latency: 1.002006ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:45:54Z" - latency: 893.863µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:44:54Z" - latency: 1.347541ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:43:54Z" - latency: 1.388346ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:42:54Z" - latency: 1.19745ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:41:54Z" - latency: 1.000855ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:40:54Z" - latency: 839.694µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:39:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T04:27:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-81-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-81.ec2.internal uid: 29e27961-be7f-4bb1-a5da-4de596c531e1 resourceVersion: "40454" uid: 8518f992-892a-4c87-90d8-3312905386a4 spec: sourcePod: network-check-source-7b678d77c7-qnjs2 targetEndpoint: aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T04:33:54Z" message: 'load-balancer-api-external: tcp connection to aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.950552ms message: 'load-balancer-api-external: tcp connection to aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:51:54Z" - latency: 6.916525ms message: 'load-balancer-api-external: resolved host name aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T04:51:54Z" - latency: 4.306965ms message: 'load-balancer-api-external: tcp connection to aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:50:54Z" - latency: 6.7846ms message: 'load-balancer-api-external: resolved host name aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T04:50:54Z" - latency: 4.823515ms message: 'load-balancer-api-external: tcp connection to aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:49:54Z" - latency: 7.011911ms message: 'load-balancer-api-external: resolved host name aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T04:49:54Z" - latency: 6.393097ms message: 'load-balancer-api-external: tcp connection to aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:48:54Z" - latency: 6.746008ms message: 'load-balancer-api-external: resolved host name aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T04:48:54Z" - latency: 8.606575ms message: 'load-balancer-api-external: tcp connection to aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:47:54Z" - latency: 7.109164ms message: 'load-balancer-api-external: resolved host name aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T04:47:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T04:27:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-81-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-81.ec2.internal uid: 29e27961-be7f-4bb1-a5da-4de596c531e1 resourceVersion: "40453" uid: 1c767c37-3046-4e7f-8b8c-87fb98804da0 spec: sourcePod: network-check-source-7b678d77c7-qnjs2 targetEndpoint: aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T04:33:54Z" message: 'load-balancer-api-internal: tcp connection to aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.914394ms message: 'load-balancer-api-internal: tcp connection to aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:51:54Z" - latency: 7.066712ms message: 'load-balancer-api-internal: resolved host name aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T04:51:54Z" - latency: 4.336005ms message: 'load-balancer-api-internal: tcp connection to aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:50:54Z" - latency: 6.733452ms message: 'load-balancer-api-internal: resolved host name aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T04:50:54Z" - latency: 5.262166ms message: 'load-balancer-api-internal: tcp connection to aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:49:54Z" - latency: 7.039056ms message: 'load-balancer-api-internal: resolved host name aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T04:49:54Z" - latency: 6.363668ms message: 'load-balancer-api-internal: tcp connection to aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:48:54Z" - latency: 6.86693ms message: 'load-balancer-api-internal: resolved host name aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T04:48:54Z" - latency: 6.292874ms message: 'load-balancer-api-internal: tcp connection to aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:47:54Z" - latency: 7.057901ms message: 'load-balancer-api-internal: resolved host name aac254c76796c469ca2787e3eb3a4709-4684210062df6939.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T04:47:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T04:27:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-81-to-network-check-target-ip-10-0-133-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-81.ec2.internal uid: 29e27961-be7f-4bb1-a5da-4de596c531e1 resourceVersion: "37383" uid: c0d7b07a-102d-493c-a4bd-b5c1a7f25db6 spec: sourcePod: network-check-source-7b678d77c7-qnjs2 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T04:34:54Z" message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.416978ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:48:54Z" - latency: 1.747334ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:47:54Z" - latency: 2.56938ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:46:54Z" - latency: 2.182591ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:45:54Z" - latency: 2.010506ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:44:54Z" - latency: 2.154918ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:43:54Z" - latency: 2.425186ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:42:54Z" - latency: 2.635197ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:41:54Z" - latency: 2.357904ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:40:54Z" - latency: 2.099ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:39:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T04:27:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-81-to-network-check-target-ip-10-0-133-81 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-81.ec2.internal uid: 29e27961-be7f-4bb1-a5da-4de596c531e1 resourceVersion: "37381" uid: 400a9e25-1d9c-4007-9546-902564833a59 spec: sourcePod: network-check-source-7b678d77c7-qnjs2 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T04:34:54Z" message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 949.369µs message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:48:54Z" - latency: 1.354611ms message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:47:54Z" - latency: 1.496801ms message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:46:54Z" - latency: 1.711163ms message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:45:54Z" - latency: 901.241µs message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:44:54Z" - latency: 1.313934ms message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:43:54Z" - latency: 1.443705ms message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:42:54Z" - latency: 1.512028ms message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:41:54Z" - latency: 1.104988ms message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:40:54Z" - latency: 879.099µs message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:39:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T04:27:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-81-to-network-check-target-ip-10-0-140-211 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-81.ec2.internal uid: 29e27961-be7f-4bb1-a5da-4de596c531e1 resourceVersion: "37382" uid: bb5f2631-7c14-4dcc-8350-a1aa2b3a0b47 spec: sourcePod: network-check-source-7b678d77c7-qnjs2 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-16T04:34:54Z" message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.218738ms message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:48:54Z" - latency: 2.102614ms message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:47:54Z" - latency: 1.994908ms message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:46:54Z" - latency: 2.228499ms message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:45:54Z" - latency: 2.280879ms message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:44:54Z" - latency: 2.008441ms message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:43:54Z" - latency: 2.032604ms message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:42:54Z" - latency: 2.331991ms message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:41:54Z" - latency: 1.977957ms message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:40:54Z" - latency: 2.125073ms message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:39:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T04:27:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-81-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-81.ec2.internal uid: 29e27961-be7f-4bb1-a5da-4de596c531e1 resourceVersion: "40452" uid: 0365ccbf-ec45-403c-be81-fe8eb3a6d808 spec: sourcePod: network-check-source-7b678d77c7-qnjs2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T04:33:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 757.577µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:51:54Z" - latency: 1.719647ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T04:51:54Z" - latency: 1.162824ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:50:54Z" - latency: 1.78837ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T04:50:54Z" - latency: 1.205454ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:49:54Z" - latency: 2.050663ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T04:49:54Z" - latency: 826.989µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:48:54Z" - latency: 1.674388ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T04:48:54Z" - latency: 756.289µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T04:47:54Z" - latency: 1.769202ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T04:47:54Z" kind: List metadata: resourceVersion: ""