apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T16:39:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-35-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-35.ec2.internal uid: ca2da8f3-b7bf-4705-a55b-ef00591a41cf resourceVersion: "50621" uid: 55ff2e60-1f60-4015-872b-cd3dbe1a18e9 spec: sourcePod: network-check-source-dbd9cf844-2mq6v targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-08T16:46:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.773008ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:14:42Z" - latency: 1.083764ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:13:42Z" - latency: 1.007128ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:12:42Z" - latency: 1.395704ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:11:42Z" - latency: 944.391µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:10:42Z" - latency: 1.367604ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:09:42Z" - latency: 999.896µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:08:42Z" - latency: 1.011259ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:07:42Z" - latency: 940.485µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:06:42Z" - latency: 1.088996ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:05:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T16:39:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-35-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-35.ec2.internal uid: ca2da8f3-b7bf-4705-a55b-ef00591a41cf resourceVersion: "45303" uid: d3654421-43dd-47bd-b194-8743d7618ef0 spec: sourcePod: network-check-source-dbd9cf844-2mq6v targetEndpoint: af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T16:45:42Z" message: 'load-balancer-api-external: tcp connection to af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.388211ms message: 'load-balancer-api-external: tcp connection to af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:09:42Z" - latency: 6.508209ms message: 'load-balancer-api-external: resolved host name af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T17:09:42Z" - latency: 3.689907ms message: 'load-balancer-api-external: tcp connection to af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:08:42Z" - latency: 7.391457ms message: 'load-balancer-api-external: resolved host name af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T17:08:42Z" - latency: 5.418725ms message: 'load-balancer-api-external: tcp connection to af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:07:42Z" - latency: 7.22456ms message: 'load-balancer-api-external: resolved host name af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T17:07:42Z" - latency: 4.145506ms message: 'load-balancer-api-external: tcp connection to af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:06:42Z" - latency: 10.995301ms message: 'load-balancer-api-external: resolved host name af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T17:06:42Z" - latency: 4.530549ms message: 'load-balancer-api-external: tcp connection to af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:05:42Z" - latency: 8.478036ms message: 'load-balancer-api-external: resolved host name af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T17:05:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T16:39:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-35-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-35.ec2.internal uid: ca2da8f3-b7bf-4705-a55b-ef00591a41cf resourceVersion: "45302" uid: d793b4f1-e24d-48fd-9b3f-654763e773c3 spec: sourcePod: network-check-source-dbd9cf844-2mq6v targetEndpoint: af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T16:45:42Z" message: 'load-balancer-api-internal: tcp connection to af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.069915ms message: 'load-balancer-api-internal: tcp connection to af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:09:42Z" - latency: 6.644233ms message: 'load-balancer-api-internal: resolved host name af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T17:09:42Z" - latency: 3.610366ms message: 'load-balancer-api-internal: tcp connection to af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:08:42Z" - latency: 7.427621ms message: 'load-balancer-api-internal: resolved host name af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T17:08:42Z" - latency: 5.062855ms message: 'load-balancer-api-internal: tcp connection to af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:07:42Z" - latency: 7.303934ms message: 'load-balancer-api-internal: resolved host name af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T17:07:42Z" - latency: 4.726317ms message: 'load-balancer-api-internal: tcp connection to af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:06:42Z" - latency: 11.016322ms message: 'load-balancer-api-internal: resolved host name af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T17:06:42Z" - latency: 4.899427ms message: 'load-balancer-api-internal: tcp connection to af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:05:42Z" - latency: 8.580854ms message: 'load-balancer-api-internal: resolved host name af7ea1820635643239d15d3f11463029-e8a04e7ccd880b04.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T17:05:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T16:39:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-35-to-network-check-target-ip-10-0-132-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-35.ec2.internal uid: ca2da8f3-b7bf-4705-a55b-ef00591a41cf resourceVersion: "50619" uid: 9ef5b7e8-bf27-488c-ad80-fd6e883cc3c3 spec: sourcePod: network-check-source-dbd9cf844-2mq6v targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-08T16:46:42Z" message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.189178ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:14:42Z" - latency: 2.180434ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:13:42Z" - latency: 2.177572ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:12:42Z" - latency: 1.865753ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:11:42Z" - latency: 2.27471ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:10:42Z" - latency: 2.239208ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:09:42Z" - latency: 2.05918ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:08:42Z" - latency: 2.468196ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:07:42Z" - latency: 2.327066ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:06:42Z" - latency: 2.115661ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:05:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T16:39:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-35-to-network-check-target-ip-10-0-141-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-35.ec2.internal uid: ca2da8f3-b7bf-4705-a55b-ef00591a41cf resourceVersion: "50618" uid: 4c410a6f-1000-44a2-9b0c-0cf6bec9dddb spec: sourcePod: network-check-source-dbd9cf844-2mq6v targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-08T16:46:42Z" message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 837.69µs message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:14:42Z" - latency: 864.762µs message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:13:42Z" - latency: 949.425µs message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:12:42Z" - latency: 1.049754ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:11:42Z" - latency: 1.293547ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:10:42Z" - latency: 946.827µs message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:09:42Z" - latency: 784.583µs message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:08:42Z" - latency: 802.115µs message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:07:42Z" - latency: 1.296607ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:06:42Z" - latency: 826.773µs message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:05:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T16:39:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-35-to-network-check-target-ip-10-0-141-92 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-35.ec2.internal uid: ca2da8f3-b7bf-4705-a55b-ef00591a41cf resourceVersion: "50620" uid: e9b4025b-784c-474d-a611-c131404d20ea spec: sourcePod: network-check-source-dbd9cf844-2mq6v targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-08T16:46:42Z" message: 'network-check-target-ip-10-0-141-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.091697ms message: 'network-check-target-ip-10-0-141-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:14:42Z" - latency: 1.963153ms message: 'network-check-target-ip-10-0-141-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:13:42Z" - latency: 1.94881ms message: 'network-check-target-ip-10-0-141-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:12:42Z" - latency: 2.11458ms message: 'network-check-target-ip-10-0-141-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:11:42Z" - latency: 2.06241ms message: 'network-check-target-ip-10-0-141-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:10:42Z" - latency: 2.015418ms message: 'network-check-target-ip-10-0-141-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:09:42Z" - latency: 1.984225ms message: 'network-check-target-ip-10-0-141-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:08:42Z" - latency: 2.063657ms message: 'network-check-target-ip-10-0-141-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:07:42Z" - latency: 2.063295ms message: 'network-check-target-ip-10-0-141-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:06:42Z" - latency: 1.986898ms message: 'network-check-target-ip-10-0-141-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:05:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T16:39:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-35-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-35.ec2.internal uid: ca2da8f3-b7bf-4705-a55b-ef00591a41cf resourceVersion: "45301" uid: 24b6ff2f-7908-4a2c-bea5-74305acc9543 spec: sourcePod: network-check-source-dbd9cf844-2mq6v targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-08T16:45:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 790.179µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:09:42Z" - latency: 1.836609ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T17:09:42Z" - latency: 915.1µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:08:42Z" - latency: 1.856492ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T17:08:42Z" - latency: 1.181533ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:07:42Z" - latency: 2.688458ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T17:07:42Z" - latency: 891.453µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:06:42Z" - latency: 1.63868ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T17:06:42Z" - latency: 1.014046ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T17:05:42Z" - latency: 1.827403ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T17:05:42Z" kind: List metadata: resourceVersion: ""