apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:23:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-92-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-92.ec2.internal uid: 041b4229-e3a4-4321-b639-f3de6673dfa2 resourceVersion: "50825" uid: 69eb60a1-4c39-45b1-9b2b-b7708f5c2d0c spec: sourcePod: network-check-source-6947749cfc-8klqn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-12T22:30:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 958.963µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:58:37Z" - latency: 925.208µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:57:37Z" - latency: 1.024595ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:56:37Z" - latency: 1.021506ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:55:37Z" - latency: 888.95µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:54:37Z" - latency: 815.812µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:53:37Z" - latency: 952.146µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:52:37Z" - latency: 1.098193ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:51:37Z" - latency: 808.598µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:50:37Z" - latency: 797.248µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:49:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:23:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-92-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-92.ec2.internal uid: 041b4229-e3a4-4321-b639-f3de6673dfa2 resourceVersion: "45406" uid: 40a6a4be-f59f-49b5-bd0c-0da8f37929b5 spec: sourcePod: network-check-source-6947749cfc-8klqn targetEndpoint: a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T22:29:37Z" message: 'load-balancer-api-external: tcp connection to a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.870321ms message: 'load-balancer-api-external: tcp connection to a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:53:37Z" - latency: 8.313794ms message: 'load-balancer-api-external: resolved host name a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:53:37Z" - latency: 4.683626ms message: 'load-balancer-api-external: tcp connection to a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:52:37Z" - latency: 8.397011ms message: 'load-balancer-api-external: resolved host name a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:52:37Z" - latency: 5.532079ms message: 'load-balancer-api-external: tcp connection to a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:51:37Z" - latency: 8.256296ms message: 'load-balancer-api-external: resolved host name a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:51:37Z" - latency: 5.113044ms message: 'load-balancer-api-external: tcp connection to a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:50:37Z" - latency: 8.672767ms message: 'load-balancer-api-external: resolved host name a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:50:37Z" - latency: 5.57241ms message: 'load-balancer-api-external: tcp connection to a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:49:37Z" - latency: 7.813385ms message: 'load-balancer-api-external: resolved host name a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:49:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:23:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-92-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-92.ec2.internal uid: 041b4229-e3a4-4321-b639-f3de6673dfa2 resourceVersion: "45405" uid: 74d176f5-83ce-447f-9d36-ffe96870dea2 spec: sourcePod: network-check-source-6947749cfc-8klqn targetEndpoint: a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T22:29:37Z" message: 'load-balancer-api-internal: tcp connection to a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.867646ms message: 'load-balancer-api-internal: tcp connection to a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:53:37Z" - latency: 8.379389ms message: 'load-balancer-api-internal: resolved host name a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:53:37Z" - latency: 4.07356ms message: 'load-balancer-api-internal: tcp connection to a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:52:37Z" - latency: 8.477148ms message: 'load-balancer-api-internal: resolved host name a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:52:37Z" - latency: 5.567236ms message: 'load-balancer-api-internal: tcp connection to a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:51:37Z" - latency: 8.219746ms message: 'load-balancer-api-internal: resolved host name a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:51:37Z" - latency: 3.716222ms message: 'load-balancer-api-internal: tcp connection to a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:50:37Z" - latency: 8.644374ms message: 'load-balancer-api-internal: resolved host name a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:50:37Z" - latency: 5.567964ms message: 'load-balancer-api-internal: tcp connection to a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:49:37Z" - latency: 7.780303ms message: 'load-balancer-api-internal: resolved host name a5548a7956fc84fc3bd8d47eeaedb086-65b229505efec11c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:49:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:23:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-92-to-network-check-target-ip-10-0-128-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-92.ec2.internal uid: 041b4229-e3a4-4321-b639-f3de6673dfa2 resourceVersion: "50822" uid: 24f2e3d9-2a00-447c-8b9f-3e12c4e7f0eb spec: sourcePod: network-check-source-6947749cfc-8klqn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-12T22:30:37Z" message: 'network-check-target-ip-10-0-128-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.656742ms message: 'network-check-target-ip-10-0-128-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:58:37Z" - latency: 2.410226ms message: 'network-check-target-ip-10-0-128-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:57:37Z" - latency: 2.092591ms message: 'network-check-target-ip-10-0-128-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:56:37Z" - latency: 2.627969ms message: 'network-check-target-ip-10-0-128-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:55:37Z" - latency: 2.316095ms message: 'network-check-target-ip-10-0-128-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:54:37Z" - latency: 2.269673ms message: 'network-check-target-ip-10-0-128-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:53:37Z" - latency: 2.362562ms message: 'network-check-target-ip-10-0-128-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:52:37Z" - latency: 2.375833ms message: 'network-check-target-ip-10-0-128-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:51:37Z" - latency: 2.418157ms message: 'network-check-target-ip-10-0-128-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:50:37Z" - latency: 2.170503ms message: 'network-check-target-ip-10-0-128-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:49:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:23:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-92-to-network-check-target-ip-10-0-128-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-92.ec2.internal uid: 041b4229-e3a4-4321-b639-f3de6673dfa2 resourceVersion: "50823" uid: db6efc20-3e6e-490d-a297-a40b5d0ae113 spec: sourcePod: network-check-source-6947749cfc-8klqn targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-12T22:30:37Z" message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.546825ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:58:37Z" - latency: 2.341758ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:57:37Z" - latency: 2.246147ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:56:37Z" - latency: 2.431966ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:55:37Z" - latency: 2.614185ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:54:37Z" - latency: 2.339663ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:53:37Z" - latency: 2.328206ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:52:37Z" - latency: 2.453589ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:51:37Z" - latency: 2.112571ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:50:37Z" - latency: 2.438621ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:49:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:23:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-92-to-network-check-target-ip-10-0-143-92 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-92.ec2.internal uid: 041b4229-e3a4-4321-b639-f3de6673dfa2 resourceVersion: "50821" uid: 8a070406-8212-4664-82c6-912533a5cc8a spec: sourcePod: network-check-source-6947749cfc-8klqn targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-12T22:30:37Z" message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.073797ms message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:58:37Z" - latency: 785.196µs message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:57:37Z" - latency: 898.737µs message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:56:37Z" - latency: 931.993µs message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:55:37Z" - latency: 1.265562ms message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:54:37Z" - latency: 727.185µs message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:53:37Z" - latency: 888.786µs message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:52:37Z" - latency: 761.565µs message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:51:37Z" - latency: 955.733µs message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:50:37Z" - latency: 1.078493ms message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:49:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:23:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-92-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-92.ec2.internal uid: 041b4229-e3a4-4321-b639-f3de6673dfa2 resourceVersion: "45404" uid: ed6ed035-4ff6-4577-b179-65989422076d spec: sourcePod: network-check-source-6947749cfc-8klqn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-12T22:29:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.108179ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:53:37Z" - latency: 1.672823ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:53:37Z" - latency: 805.411µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:52:37Z" - latency: 1.675456ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:52:37Z" - latency: 980.29µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:51:37Z" - latency: 2.119927ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:51:37Z" - latency: 796.777µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:50:37Z" - latency: 1.837133ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:50:37Z" - latency: 751.749µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:49:37Z" - latency: 1.631102ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:49:37Z" kind: List metadata: resourceVersion: ""