apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:28:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-249-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-249.ec2.internal uid: 19160e17-820c-4258-b358-65e7035a9957 resourceVersion: "33133" uid: a0aa0fa3-a2ac-4509-88e2-372ef0478529 spec: sourcePod: network-check-source-7f44b6dd87-rbnvs targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-26T11:35:34Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 716µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:17:34Z" - latency: 734.605µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:16:34Z" - latency: 1.334731ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:15:34Z" - latency: 1.275998ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:14:34Z" - latency: 848.152µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:13:34Z" - latency: 722.546µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:12:34Z" - latency: 843.256µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:11:34Z" - latency: 895.317µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:10:34Z" - latency: 787.707µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:09:34Z" - latency: 964.523µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:08:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:28:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-249-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-249.ec2.internal uid: 19160e17-820c-4258-b358-65e7035a9957 resourceVersion: "35300" uid: 33701dd7-5c52-4a86-b7a8-942939c49228 spec: sourcePod: network-check-source-7f44b6dd87-rbnvs targetEndpoint: a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T11:34:34Z" message: 'load-balancer-api-external: tcp connection to a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.867971ms message: 'load-balancer-api-external: tcp connection to a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:22:34Z" - latency: 6.780736ms message: 'load-balancer-api-external: resolved host name a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:22:34Z" - latency: 6.340602ms message: 'load-balancer-api-external: tcp connection to a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:21:34Z" - latency: 7.383297ms message: 'load-balancer-api-external: resolved host name a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:21:34Z" - latency: 5.108886ms message: 'load-balancer-api-external: tcp connection to a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:20:34Z" - latency: 8.238387ms message: 'load-balancer-api-external: resolved host name a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:20:34Z" - latency: 5.333001ms message: 'load-balancer-api-external: tcp connection to a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:19:34Z" - latency: 7.389156ms message: 'load-balancer-api-external: resolved host name a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:19:34Z" - latency: 5.922229ms message: 'load-balancer-api-external: tcp connection to a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:18:34Z" - latency: 6.575271ms message: 'load-balancer-api-external: resolved host name a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:18:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:28:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-249-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-249.ec2.internal uid: 19160e17-820c-4258-b358-65e7035a9957 resourceVersion: "35299" uid: cb7098e6-ae85-436e-ac5c-941efbe4e77b spec: sourcePod: network-check-source-7f44b6dd87-rbnvs targetEndpoint: a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T11:34:34Z" message: 'load-balancer-api-internal: tcp connection to a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.865328ms message: 'load-balancer-api-internal: tcp connection to a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:22:34Z" - latency: 6.846689ms message: 'load-balancer-api-internal: resolved host name a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:22:34Z" - latency: 6.329502ms message: 'load-balancer-api-internal: tcp connection to a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:21:34Z" - latency: 7.471393ms message: 'load-balancer-api-internal: resolved host name a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:21:34Z" - latency: 5.295402ms message: 'load-balancer-api-internal: tcp connection to a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:20:34Z" - latency: 8.324836ms message: 'load-balancer-api-internal: resolved host name a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:20:34Z" - latency: 5.143638ms message: 'load-balancer-api-internal: tcp connection to a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:19:34Z" - latency: 7.436853ms message: 'load-balancer-api-internal: resolved host name a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:19:34Z" - latency: 5.426761ms message: 'load-balancer-api-internal: tcp connection to a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:18:34Z" - latency: 6.551784ms message: 'load-balancer-api-internal: resolved host name a036beb929e8c48a8ad35a8ba23eac0d-0b7120d2022a4409.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:18:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:28:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-249-to-network-check-target-ip-10-0-129-97 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-249.ec2.internal uid: 19160e17-820c-4258-b358-65e7035a9957 resourceVersion: "33132" uid: 432b02d0-30c5-4c47-8b28-47a4946da447 spec: sourcePod: network-check-source-7f44b6dd87-rbnvs targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-26T11:35:34Z" message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.864961ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:17:34Z" - latency: 1.80534ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:16:34Z" - latency: 1.745276ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:15:34Z" - latency: 2.286714ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:14:34Z" - latency: 1.783332ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:13:34Z" - latency: 1.876895ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:12:34Z" - latency: 1.864672ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:11:34Z" - latency: 1.836747ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:10:34Z" - latency: 1.839307ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:09:34Z" - latency: 1.956919ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:08:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:28:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-249-to-network-check-target-ip-10-0-133-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-249.ec2.internal uid: 19160e17-820c-4258-b358-65e7035a9957 resourceVersion: "33130" uid: f7e5dac1-9052-407c-b3ee-2fa4e951dd67 spec: sourcePod: network-check-source-7f44b6dd87-rbnvs targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-26T11:35:34Z" message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 801.904µs message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:17:34Z" - latency: 964.44µs message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:16:34Z" - latency: 827.884µs message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:15:34Z" - latency: 1.51505ms message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:14:34Z" - latency: 1.227085ms message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:13:34Z" - latency: 883µs message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:12:34Z" - latency: 816.065µs message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:11:34Z" - latency: 880.7µs message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:10:34Z" - latency: 1.018892ms message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:09:34Z" - latency: 851.842µs message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:08:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:28:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-249-to-network-check-target-ip-10-0-135-71 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-249.ec2.internal uid: 19160e17-820c-4258-b358-65e7035a9957 resourceVersion: "33131" uid: 996748a3-de57-4cd4-94b8-7d5a5b3dd6a4 spec: sourcePod: network-check-source-7f44b6dd87-rbnvs targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-26T11:35:34Z" message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.303224ms message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:17:34Z" - latency: 2.082484ms message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:16:34Z" - latency: 2.157246ms message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:15:34Z" - latency: 2.122222ms message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:14:34Z" - latency: 2.058909ms message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:13:34Z" - latency: 2.161518ms message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:12:34Z" - latency: 2.123515ms message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:11:34Z" - latency: 2.249508ms message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:10:34Z" - latency: 2.254634ms message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:09:34Z" - latency: 2.267059ms message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:08:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:28:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-249-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-249.ec2.internal uid: 19160e17-820c-4258-b358-65e7035a9957 resourceVersion: "35298" uid: e47609d6-0a9a-411c-be97-ca4e2f7ccc75 spec: sourcePod: network-check-source-7f44b6dd87-rbnvs targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-26T11:34:34Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.102865ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:22:34Z" - latency: 1.784101ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T12:22:34Z" - latency: 1.08541ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:21:34Z" - latency: 1.957093ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T12:21:34Z" - latency: 933.105µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:20:34Z" - latency: 1.705713ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T12:20:34Z" - latency: 824.392µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:19:34Z" - latency: 1.608797ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T12:19:34Z" - latency: 1.144529ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:18:34Z" - latency: 1.702444ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T12:18:34Z" kind: List metadata: resourceVersion: ""