apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:05:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-197-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-197.ec2.internal uid: 9b7d628c-951f-4e0a-8218-8a91fa13cf9b resourceVersion: "75691" uid: 12faea01-f658-4620-a0d2-578f32e047ec spec: sourcePod: network-check-source-7d88cb55d8-nqks8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T21:12:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.343329ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:54:21Z" - latency: 1.502593ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:53:21Z" - latency: 1.041554ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:52:21Z" - latency: 1.274043ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:51:21Z" - latency: 1.237661ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:50:21Z" - latency: 1.017461ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:49:21Z" - latency: 1.172758ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:48:21Z" - latency: 990.054µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:47:21Z" - latency: 1.15979ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:46:21Z" - latency: 1.291561ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:45:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:05:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-197-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-197.ec2.internal uid: 9b7d628c-951f-4e0a-8218-8a91fa13cf9b resourceVersion: "73652" uid: 2d4e8c57-3399-4bdd-8159-7e0a1e7b62d9 spec: sourcePod: network-check-source-7d88cb55d8-nqks8 targetEndpoint: a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T21:11:21Z" message: 'load-balancer-api-external: tcp connection to a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.528348ms message: 'load-balancer-api-external: tcp connection to a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:53:21Z" - latency: 7.485607ms message: 'load-balancer-api-external: resolved host name a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:53:21Z" - latency: 5.229824ms message: 'load-balancer-api-external: tcp connection to a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:52:21Z" - latency: 9.734114ms message: 'load-balancer-api-external: resolved host name a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:52:21Z" - latency: 6.345816ms message: 'load-balancer-api-external: tcp connection to a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:51:21Z" - latency: 9.359616ms message: 'load-balancer-api-external: resolved host name a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:51:21Z" - latency: 4.618715ms message: 'load-balancer-api-external: tcp connection to a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:50:21Z" - latency: 7.202821ms message: 'load-balancer-api-external: resolved host name a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:50:21Z" - latency: 5.417335ms message: 'load-balancer-api-external: tcp connection to a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:49:21Z" - latency: 6.429978ms message: 'load-balancer-api-external: resolved host name a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:49:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:05:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-197-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-197.ec2.internal uid: 9b7d628c-951f-4e0a-8218-8a91fa13cf9b resourceVersion: "73653" uid: d76d81f4-e8b8-4ed7-9bd7-48106a137444 spec: sourcePod: network-check-source-7d88cb55d8-nqks8 targetEndpoint: a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T21:11:21Z" message: 'load-balancer-api-internal: tcp connection to a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.522941ms message: 'load-balancer-api-internal: tcp connection to a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:53:21Z" - latency: 7.551518ms message: 'load-balancer-api-internal: resolved host name a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:53:21Z" - latency: 5.842204ms message: 'load-balancer-api-internal: tcp connection to a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:52:21Z" - latency: 9.682665ms message: 'load-balancer-api-internal: resolved host name a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:52:21Z" - latency: 4.080815ms message: 'load-balancer-api-internal: tcp connection to a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:51:21Z" - latency: 9.306624ms message: 'load-balancer-api-internal: resolved host name a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:51:21Z" - latency: 4.050188ms message: 'load-balancer-api-internal: tcp connection to a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:50:21Z" - latency: 7.2227ms message: 'load-balancer-api-internal: resolved host name a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:50:21Z" - latency: 5.410246ms message: 'load-balancer-api-internal: tcp connection to a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:49:21Z" - latency: 6.484355ms message: 'load-balancer-api-internal: resolved host name a82ff78994100463786bf9cae788bb40-86c8b874b0dce100.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:49:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:05:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-197-to-network-check-target-ip-10-0-131-197 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-197.ec2.internal uid: 9b7d628c-951f-4e0a-8218-8a91fa13cf9b resourceVersion: "75688" uid: 37f1d6a3-6a90-4392-9bb0-75b5031526f4 spec: sourcePod: network-check-source-7d88cb55d8-nqks8 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T21:12:21Z" message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.232548ms message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:54:21Z" - latency: 958.967µs message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:53:21Z" - latency: 1.510469ms message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:52:21Z" - latency: 902.039µs message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:51:21Z" - latency: 1.487838ms message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:50:21Z" - latency: 1.012453ms message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:49:21Z" - latency: 1.830652ms message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:48:21Z" - latency: 1.255591ms message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:47:21Z" - latency: 909.381µs message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:46:21Z" - latency: 902.195µs message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:45:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:05:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-197-to-network-check-target-ip-10-0-140-33 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-197.ec2.internal uid: 9b7d628c-951f-4e0a-8218-8a91fa13cf9b resourceVersion: "75690" uid: eb49bf70-e156-436d-a65b-9c85babaf5db spec: sourcePod: network-check-source-7d88cb55d8-nqks8 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-27T21:12:21Z" message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.589064ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:54:21Z" - latency: 2.66361ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:53:21Z" - latency: 2.195036ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:52:21Z" - latency: 2.365326ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:51:21Z" - latency: 2.141779ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:50:21Z" - latency: 1.936147ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:49:21Z" - latency: 2.287484ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:48:21Z" - latency: 2.142028ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:47:21Z" - latency: 2.175865ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:46:21Z" - latency: 2.166974ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:45:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:05:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-197-to-network-check-target-ip-10-0-143-7 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-197.ec2.internal uid: 9b7d628c-951f-4e0a-8218-8a91fa13cf9b resourceVersion: "75689" uid: d8da4e82-3121-43a7-9154-41ed7602b644 spec: sourcePod: network-check-source-7d88cb55d8-nqks8 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-27T21:12:21Z" message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.525135ms message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:54:21Z" - latency: 2.474681ms message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:53:21Z" - latency: 2.073017ms message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:52:21Z" - latency: 2.412108ms message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:51:21Z" - latency: 2.338637ms message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:50:21Z" - latency: 1.923813ms message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:49:21Z" - latency: 2.143281ms message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:48:21Z" - latency: 2.212416ms message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:47:21Z" - latency: 1.869096ms message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:46:21Z" - latency: 1.983436ms message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:45:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:05:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-197-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-197.ec2.internal uid: 9b7d628c-951f-4e0a-8218-8a91fa13cf9b resourceVersion: "73650" uid: 94ca98bd-0ce4-4db2-8b62-d39ca3e62bf2 spec: sourcePod: network-check-source-7d88cb55d8-nqks8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T21:11:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.442659ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:53:21Z" - latency: 2.030397ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T21:53:21Z" - latency: 1.338528ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:52:21Z" - latency: 1.892932ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T21:52:21Z" - latency: 899.627µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:51:21Z" - latency: 1.890903ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T21:51:21Z" - latency: 1.443486ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:50:21Z" - latency: 1.775416ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T21:50:21Z" - latency: 1.138251ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:49:21Z" - latency: 1.991621ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T21:49:21Z" kind: List metadata: resourceVersion: ""