apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T09:10:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-202-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-202.ec2.internal uid: eee919a6-fce0-4461-af78-06c0bf84cb1f resourceVersion: "77862" uid: f10fcf26-a7fa-440f-8a9f-0ff6c20f9def spec: sourcePod: network-check-source-65bdbbff45-jx72h targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T09:18:00Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.02774ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:07:00Z" - latency: 975.569µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:06:00Z" - latency: 1.665423ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:05:00Z" - latency: 1.316478ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:04:00Z" - latency: 1.31419ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:03:00Z" - latency: 957.778µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:02:00Z" - latency: 1.17665ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:01:00Z" - latency: 2.021306ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:00:00Z" - latency: 1.152627ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T09:59:00Z" - latency: 958.52µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T09:58:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T09:10:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-202-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-202.ec2.internal uid: eee919a6-fce0-4461-af78-06c0bf84cb1f resourceVersion: "75778" uid: 852904ad-f24f-4bba-8287-dedea4bee289 spec: sourcePod: network-check-source-65bdbbff45-jx72h targetEndpoint: a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T09:17:00Z" message: 'load-balancer-api-external: tcp connection to a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.289892ms message: 'load-balancer-api-external: tcp connection to a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:05:00Z" - latency: 9.105538ms message: 'load-balancer-api-external: resolved host name a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:05:00Z" - latency: 5.944546ms message: 'load-balancer-api-external: tcp connection to a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:04:00Z" - latency: 9.540417ms message: 'load-balancer-api-external: resolved host name a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:04:00Z" - latency: 6.834809ms message: 'load-balancer-api-external: tcp connection to a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:03:00Z" - latency: 8.835456ms message: 'load-balancer-api-external: resolved host name a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:03:00Z" - latency: 4.417274ms message: 'load-balancer-api-external: tcp connection to a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:02:00Z" - latency: 9.128139ms message: 'load-balancer-api-external: resolved host name a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:02:00Z" - latency: 5.478781ms message: 'load-balancer-api-external: tcp connection to a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:01:00Z" - latency: 8.769189ms message: 'load-balancer-api-external: resolved host name a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:01:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T09:10:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-202-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-202.ec2.internal uid: eee919a6-fce0-4461-af78-06c0bf84cb1f resourceVersion: "75779" uid: 31b53fe1-90f1-40ff-b9af-b45aa6f2a9ec spec: sourcePod: network-check-source-65bdbbff45-jx72h targetEndpoint: a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T09:17:00Z" message: 'load-balancer-api-internal: tcp connection to a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.429731ms message: 'load-balancer-api-internal: tcp connection to a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:05:00Z" - latency: 9.136854ms message: 'load-balancer-api-internal: resolved host name a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:05:00Z" - latency: 5.925954ms message: 'load-balancer-api-internal: tcp connection to a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:04:00Z" - latency: 9.575193ms message: 'load-balancer-api-internal: resolved host name a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:04:00Z" - latency: 5.247972ms message: 'load-balancer-api-internal: tcp connection to a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:03:00Z" - latency: 8.747635ms message: 'load-balancer-api-internal: resolved host name a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:03:00Z" - latency: 3.953486ms message: 'load-balancer-api-internal: tcp connection to a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:02:00Z" - latency: 9.21217ms message: 'load-balancer-api-internal: resolved host name a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:02:00Z" - latency: 5.084284ms message: 'load-balancer-api-internal: tcp connection to a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:01:00Z" - latency: 8.815196ms message: 'load-balancer-api-internal: resolved host name a6c079c7dd83b457f9c0039fd157edd8-85fe8f43b13ed77c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T10:01:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T09:10:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-202-to-network-check-target-ip-10-0-136-20 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-202.ec2.internal uid: eee919a6-fce0-4461-af78-06c0bf84cb1f resourceVersion: "77861" uid: 8118c045-2fb1-4b6e-94f8-308b26844272 spec: sourcePod: network-check-source-65bdbbff45-jx72h targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T09:18:00Z" message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.426369ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:07:00Z" - latency: 3.074546ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:06:00Z" - latency: 2.29998ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:05:00Z" - latency: 2.698585ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:04:00Z" - latency: 2.467066ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:03:00Z" - latency: 2.292616ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:02:00Z" - latency: 2.649802ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:01:00Z" - latency: 2.607645ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:00:00Z" - latency: 2.600923ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T09:59:00Z" - latency: 2.258551ms message: 'network-check-target-ip-10-0-136-20: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T09:58:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T09:10:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-202-to-network-check-target-ip-10-0-143-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-202.ec2.internal uid: eee919a6-fce0-4461-af78-06c0bf84cb1f resourceVersion: "77860" uid: a404f944-b549-4f95-9561-cb40b25fed11 spec: sourcePod: network-check-source-65bdbbff45-jx72h targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-04T09:18:00Z" message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.479766ms message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:07:00Z" - latency: 2.460448ms message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:06:00Z" - latency: 2.632111ms message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:05:00Z" - latency: 2.820034ms message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:04:00Z" - latency: 2.484441ms message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:03:00Z" - latency: 2.172779ms message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:02:00Z" - latency: 2.551225ms message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:01:00Z" - latency: 2.632964ms message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:00:00Z" - latency: 2.583167ms message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T09:59:00Z" - latency: 2.223841ms message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T09:58:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T09:10:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-202-to-network-check-target-ip-10-0-143-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-202.ec2.internal uid: eee919a6-fce0-4461-af78-06c0bf84cb1f resourceVersion: "77859" uid: 3540c151-6d28-450a-b858-2fee56178ecc spec: sourcePod: network-check-source-65bdbbff45-jx72h targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-04T09:18:00Z" message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 990.06µs message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:07:00Z" - latency: 1.389133ms message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:06:00Z" - latency: 1.03348ms message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:05:00Z" - latency: 1.686563ms message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:04:00Z" - latency: 1.008761ms message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:03:00Z" - latency: 1.173999ms message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:02:00Z" - latency: 1.46452ms message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:01:00Z" - latency: 1.627386ms message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:00:00Z" - latency: 1.970745ms message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T09:59:00Z" - latency: 945.657µs message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T09:58:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T09:10:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-202-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-202.ec2.internal uid: eee919a6-fce0-4461-af78-06c0bf84cb1f resourceVersion: "75777" uid: 40ce47bd-17a9-47d0-bef7-108c7e63d29c spec: sourcePod: network-check-source-65bdbbff45-jx72h targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T09:17:00Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.195285ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:05:00Z" - latency: 1.994777ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T10:05:00Z" - latency: 1.029379ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:04:00Z" - latency: 1.763178ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T10:04:00Z" - latency: 981.68µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:03:00Z" - latency: 1.748297ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T10:03:00Z" - latency: 1.171849ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:02:00Z" - latency: 2.415514ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T10:02:00Z" - latency: 951.385µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T10:01:00Z" - latency: 1.8294ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T10:01:00Z" kind: List metadata: resourceVersion: ""