apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:03:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-226-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-226.ec2.internal uid: b8efca18-98bc-44be-81b2-fa116c6e5959 resourceVersion: "16566" uid: 70a9b9a3-af19-4acf-80ab-8c87f2c647b5 spec: sourcePod: network-check-source-7d88cb55d8-ct7lq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T17:10:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.333639ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:17:23Z" - latency: 1.11305ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:16:23Z" - latency: 1.071852ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:15:23Z" - latency: 1.303579ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:14:23Z" - latency: 959.419µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:13:23Z" - latency: 1.140762ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:12:23Z" - latency: 989.172µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:11:23Z" - latency: 1.15208ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:10:23Z" - latency: 1.260012ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:09:23Z" - latency: 943.432µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:08:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:03:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-226-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-226.ec2.internal uid: b8efca18-98bc-44be-81b2-fa116c6e5959 resourceVersion: "15824" uid: 2aca85d8-9b75-4fa6-87a5-cab234735bae spec: sourcePod: network-check-source-7d88cb55d8-ct7lq targetEndpoint: a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T17:09:23Z" message: 'load-balancer-api-external: tcp connection to a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.812034ms message: 'load-balancer-api-external: tcp connection to a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:15:23Z" - latency: 8.386202ms message: 'load-balancer-api-external: resolved host name a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:15:23Z" - latency: 6.681393ms message: 'load-balancer-api-external: tcp connection to a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:14:23Z" - latency: 9.734883ms message: 'load-balancer-api-external: resolved host name a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:14:23Z" - latency: 4.669018ms message: 'load-balancer-api-external: tcp connection to a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:13:23Z" - latency: 9.31304ms message: 'load-balancer-api-external: resolved host name a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:13:23Z" - latency: 4.497623ms message: 'load-balancer-api-external: tcp connection to a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:12:23Z" - latency: 9.712526ms message: 'load-balancer-api-external: resolved host name a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:12:23Z" - latency: 5.015705ms message: 'load-balancer-api-external: tcp connection to a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:11:23Z" - latency: 8.947714ms message: 'load-balancer-api-external: resolved host name a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:11:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:03:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-226-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-226.ec2.internal uid: b8efca18-98bc-44be-81b2-fa116c6e5959 resourceVersion: "15823" uid: f1fe3bcf-f23d-4458-97b6-5eb0b4e5c052 spec: sourcePod: network-check-source-7d88cb55d8-ct7lq targetEndpoint: a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T17:09:23Z" message: 'load-balancer-api-internal: tcp connection to a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.79764ms message: 'load-balancer-api-internal: tcp connection to a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:15:23Z" - latency: 8.487128ms message: 'load-balancer-api-internal: resolved host name a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:15:23Z" - latency: 6.719075ms message: 'load-balancer-api-internal: tcp connection to a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:14:23Z" - latency: 9.609245ms message: 'load-balancer-api-internal: resolved host name a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:14:23Z" - latency: 4.682356ms message: 'load-balancer-api-internal: tcp connection to a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:13:23Z" - latency: 9.347129ms message: 'load-balancer-api-internal: resolved host name a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:13:23Z" - latency: 4.497357ms message: 'load-balancer-api-internal: tcp connection to a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:12:23Z" - latency: 9.606761ms message: 'load-balancer-api-internal: resolved host name a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:12:23Z" - latency: 5.004581ms message: 'load-balancer-api-internal: tcp connection to a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:11:23Z" - latency: 8.990166ms message: 'load-balancer-api-internal: resolved host name a990ec2990f9c424a9c3c990ffda682a-5a76b87d64347bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:11:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:03:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-226-to-network-check-target-ip-10-0-133-247 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-226.ec2.internal uid: b8efca18-98bc-44be-81b2-fa116c6e5959 resourceVersion: "16564" uid: e94e92bc-1876-4146-90ed-273419042f96 spec: sourcePod: network-check-source-7d88cb55d8-ct7lq targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:10:23Z" message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.46241ms message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:17:23Z" - latency: 2.053121ms message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:16:23Z" - latency: 2.138223ms message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:15:23Z" - latency: 2.157753ms message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:14:23Z" - latency: 2.060305ms message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:13:23Z" - latency: 2.212204ms message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:12:23Z" - latency: 2.203606ms message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:11:23Z" - latency: 1.998288ms message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:10:23Z" - latency: 2.320116ms message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:09:23Z" - latency: 2.316065ms message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:08:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:03:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-226-to-network-check-target-ip-10-0-136-196 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-226.ec2.internal uid: b8efca18-98bc-44be-81b2-fa116c6e5959 resourceVersion: "16563" uid: 2dd0a718-b413-44bb-8741-40e8089dad20 spec: sourcePod: network-check-source-7d88cb55d8-ct7lq targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:10:23Z" message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.377918ms message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:17:23Z" - latency: 2.423878ms message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:16:23Z" - latency: 2.240225ms message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:15:23Z" - latency: 2.185301ms message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:14:23Z" - latency: 2.255695ms message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:13:23Z" - latency: 2.064696ms message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:12:23Z" - latency: 2.011916ms message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:11:23Z" - latency: 2.164359ms message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:10:23Z" - latency: 2.254125ms message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:09:23Z" - latency: 2.206667ms message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:08:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:03:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-226-to-network-check-target-ip-10-0-136-226 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-226.ec2.internal uid: b8efca18-98bc-44be-81b2-fa116c6e5959 resourceVersion: "16562" uid: dddaad3b-333f-44b9-9de3-1adfcc9c69e7 spec: sourcePod: network-check-source-7d88cb55d8-ct7lq targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:10:23Z" message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.551148ms message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:17:23Z" - latency: 1.053942ms message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:16:23Z" - latency: 914.606µs message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:15:23Z" - latency: 797.195µs message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:14:23Z" - latency: 918.719µs message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:13:23Z" - latency: 1.132032ms message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:12:23Z" - latency: 935.233µs message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:11:23Z" - latency: 945.552µs message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:10:23Z" - latency: 1.44008ms message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:09:23Z" - latency: 1.570803ms message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:08:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:03:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-226-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-226.ec2.internal uid: b8efca18-98bc-44be-81b2-fa116c6e5959 resourceVersion: "15821" uid: 58869469-c9de-48d6-ba2a-e52ac186d602 spec: sourcePod: network-check-source-7d88cb55d8-ct7lq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T17:09:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 828.054µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:15:23Z" - latency: 2.131209ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T17:15:23Z" - latency: 831.596µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:14:23Z" - latency: 2.048285ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T17:14:23Z" - latency: 1.043443ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:13:23Z" - latency: 1.770336ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T17:13:23Z" - latency: 1.014965ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:12:23Z" - latency: 2.28444ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T17:12:23Z" - latency: 989.074µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:11:23Z" - latency: 1.873683ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T17:11:23Z" kind: List metadata: resourceVersion: ""