apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T13:36:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-218-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-218.ec2.internal uid: 37083be1-a3d4-4bdc-9f9d-9216762fc333 resourceVersion: "19365" uid: 5b250615-9863-4e8b-bda2-568adaf68ab2 spec: sourcePod: network-check-source-7f44b6dd87-xpq42 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-26T13:43:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.196385ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:04:25Z" - latency: 746.219µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:03:25Z" - latency: 1.112239ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:02:25Z" - latency: 929.636µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:01:25Z" - latency: 830.671µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:00:25Z" - latency: 787.599µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:59:25Z" - latency: 830.539µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:58:25Z" - latency: 1.032612ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:57:25Z" - latency: 779.331µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:56:25Z" - latency: 681.182µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:55:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T13:36:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-218-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-218.ec2.internal uid: 37083be1-a3d4-4bdc-9f9d-9216762fc333 resourceVersion: "17644" uid: 70756356-1981-4647-b23b-d6866d9af0f6 spec: sourcePod: network-check-source-7f44b6dd87-xpq42 targetEndpoint: a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T13:42:25Z" message: 'load-balancer-api-external: tcp connection to a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.939161ms message: 'load-balancer-api-external: tcp connection to a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:00:25Z" - latency: 5.950571ms message: 'load-balancer-api-external: resolved host name a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T14:00:25Z" - latency: 4.452662ms message: 'load-balancer-api-external: tcp connection to a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:59:25Z" - latency: 6.609185ms message: 'load-balancer-api-external: resolved host name a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T13:59:25Z" - latency: 5.012859ms message: 'load-balancer-api-external: tcp connection to a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:58:25Z" - latency: 8.136517ms message: 'load-balancer-api-external: resolved host name a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T13:58:25Z" - latency: 4.317133ms message: 'load-balancer-api-external: tcp connection to a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:57:25Z" - latency: 6.300507ms message: 'load-balancer-api-external: resolved host name a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T13:57:25Z" - latency: 5.655859ms message: 'load-balancer-api-external: tcp connection to a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:56:25Z" - latency: 5.872295ms message: 'load-balancer-api-external: resolved host name a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T13:56:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T13:36:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-218-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-218.ec2.internal uid: 37083be1-a3d4-4bdc-9f9d-9216762fc333 resourceVersion: "17643" uid: 424ecbfb-526f-46e8-a652-25ec76f2a0f4 spec: sourcePod: network-check-source-7f44b6dd87-xpq42 targetEndpoint: a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T13:42:25Z" message: 'load-balancer-api-internal: tcp connection to a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.932795ms message: 'load-balancer-api-internal: tcp connection to a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:00:25Z" - latency: 5.902435ms message: 'load-balancer-api-internal: resolved host name a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T14:00:25Z" - latency: 4.098937ms message: 'load-balancer-api-internal: tcp connection to a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:59:25Z" - latency: 6.59647ms message: 'load-balancer-api-internal: resolved host name a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T13:59:25Z" - latency: 5.016489ms message: 'load-balancer-api-internal: tcp connection to a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:58:25Z" - latency: 8.058753ms message: 'load-balancer-api-internal: resolved host name a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T13:58:25Z" - latency: 4.087966ms message: 'load-balancer-api-internal: tcp connection to a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:57:25Z" - latency: 6.254398ms message: 'load-balancer-api-internal: resolved host name a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T13:57:25Z" - latency: 5.430063ms message: 'load-balancer-api-internal: tcp connection to a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:56:25Z" - latency: 5.830359ms message: 'load-balancer-api-internal: resolved host name a3c9ac8ee919b4bbeb060dc58184ec90-176d655678fb4375.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T13:56:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T13:36:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-218-to-network-check-target-ip-10-0-131-204 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-218.ec2.internal uid: 37083be1-a3d4-4bdc-9f9d-9216762fc333 resourceVersion: "19364" uid: ca6d2127-e7bd-472d-887a-2bcea00403e7 spec: sourcePod: network-check-source-7f44b6dd87-xpq42 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T13:43:25Z" message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.410491ms message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:04:25Z" - latency: 1.992373ms message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:03:25Z" - latency: 1.884178ms message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:02:25Z" - latency: 1.816284ms message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:01:25Z" - latency: 1.808903ms message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:00:25Z" - latency: 1.80758ms message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:59:25Z" - latency: 1.906096ms message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:58:25Z" - latency: 1.768265ms message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:57:25Z" - latency: 1.827433ms message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:56:25Z" - latency: 1.837264ms message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:55:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T13:36:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-218-to-network-check-target-ip-10-0-136-179 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-218.ec2.internal uid: 37083be1-a3d4-4bdc-9f9d-9216762fc333 resourceVersion: "19362" uid: abf017ea-face-41a3-98f6-fd9b6c07ebd0 spec: sourcePod: network-check-source-7f44b6dd87-xpq42 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T13:43:25Z" message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.661156ms message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:04:25Z" - latency: 1.605636ms message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:03:25Z" - latency: 1.516519ms message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:02:25Z" - latency: 1.81946ms message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:01:25Z" - latency: 1.65168ms message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:00:25Z" - latency: 1.592922ms message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:59:25Z" - latency: 1.692461ms message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:58:25Z" - latency: 1.699318ms message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:57:25Z" - latency: 1.621702ms message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:56:25Z" - latency: 1.484426ms message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:55:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T13:36:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-218-to-network-check-target-ip-10-0-143-218 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-218.ec2.internal uid: 37083be1-a3d4-4bdc-9f9d-9216762fc333 resourceVersion: "19363" uid: 22d18e15-87e7-44e9-b274-8219a60791ea spec: sourcePod: network-check-source-7f44b6dd87-xpq42 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-26T13:43:25Z" message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.102171ms message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:04:25Z" - latency: 1.092388ms message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:03:25Z" - latency: 959.764µs message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:02:25Z" - latency: 767.145µs message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:01:25Z" - latency: 675.484µs message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:00:25Z" - latency: 941.074µs message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:59:25Z" - latency: 693.115µs message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:58:25Z" - latency: 706.245µs message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:57:25Z" - latency: 699.752µs message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:56:25Z" - latency: 923.878µs message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:55:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T13:36:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-218-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-218.ec2.internal uid: 37083be1-a3d4-4bdc-9f9d-9216762fc333 resourceVersion: "17642" uid: 89478036-c11f-455e-9eb8-c994bbd8efeb spec: sourcePod: network-check-source-7f44b6dd87-xpq42 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-26T13:42:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 845.387µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T14:00:25Z" - latency: 1.431672ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T14:00:25Z" - latency: 805.413µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:59:25Z" - latency: 1.612509ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T13:59:25Z" - latency: 818.584µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:58:25Z" - latency: 1.450322ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T13:58:25Z" - latency: 887.148µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:57:25Z" - latency: 1.384425ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T13:57:25Z" - latency: 783.713µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T13:56:25Z" - latency: 1.543451ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T13:56:25Z" kind: List metadata: resourceVersion: ""