apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:11:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-0-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-0.ec2.internal uid: a4891cc0-fe0e-4201-8290-8d455b56aec2 resourceVersion: "56349" uid: 911cd2a0-fa30-4e97-ab78-9b3ab33f4c08 spec: sourcePod: network-check-source-869dcfcdcd-msxnv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T16:18: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.220805ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:46:25Z" - latency: 964.445µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:45:25Z" - latency: 857.061µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:44:25Z" - latency: 957.847µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:43:25Z" - latency: 1.14314ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:42:25Z" - latency: 1.011759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:41:25Z" - latency: 950.019µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:40:25Z" - latency: 1.104053ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:39:25Z" - latency: 878.654µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:38:25Z" - latency: 885.838µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:37:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:11:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-0-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-0.ec2.internal uid: a4891cc0-fe0e-4201-8290-8d455b56aec2 resourceVersion: "57389" uid: ee152a4c-b642-45d2-a995-850b4c45c1f6 spec: sourcePod: network-check-source-869dcfcdcd-msxnv targetEndpoint: ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T16:17:25Z" message: 'load-balancer-api-external: tcp connection to ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.581109ms message: 'load-balancer-api-external: tcp connection to ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:47:25Z" - latency: 8.592922ms message: 'load-balancer-api-external: resolved host name ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:47:25Z" - latency: 4.015084ms message: 'load-balancer-api-external: tcp connection to ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:46:25Z" - latency: 8.85322ms message: 'load-balancer-api-external: resolved host name ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:46:25Z" - latency: 5.599852ms message: 'load-balancer-api-external: tcp connection to ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:45:25Z" - latency: 8.83147ms message: 'load-balancer-api-external: resolved host name ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:45:25Z" - latency: 4.922492ms message: 'load-balancer-api-external: tcp connection to ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:44:25Z" - latency: 8.138884ms message: 'load-balancer-api-external: resolved host name ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:44:25Z" - latency: 4.761067ms message: 'load-balancer-api-external: tcp connection to ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:43:25Z" - latency: 8.459808ms message: 'load-balancer-api-external: resolved host name ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:43:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:11:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-0-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-0.ec2.internal uid: a4891cc0-fe0e-4201-8290-8d455b56aec2 resourceVersion: "57388" uid: 4aa7eb8c-c1b0-4ab5-8681-38b1f1fae33c spec: sourcePod: network-check-source-869dcfcdcd-msxnv targetEndpoint: ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T16:17:25Z" message: 'load-balancer-api-internal: tcp connection to ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.540411ms message: 'load-balancer-api-internal: tcp connection to ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:47:25Z" - latency: 8.67816ms message: 'load-balancer-api-internal: resolved host name ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:47:25Z" - latency: 3.902652ms message: 'load-balancer-api-internal: tcp connection to ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:46:25Z" - latency: 8.966894ms message: 'load-balancer-api-internal: resolved host name ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:46:25Z" - latency: 4.195841ms message: 'load-balancer-api-internal: tcp connection to ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:45:25Z" - latency: 8.950658ms message: 'load-balancer-api-internal: resolved host name ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:45:25Z" - latency: 3.640057ms message: 'load-balancer-api-internal: tcp connection to ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:44:25Z" - latency: 8.162783ms message: 'load-balancer-api-internal: resolved host name ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:44:25Z" - latency: 4.848813ms message: 'load-balancer-api-internal: tcp connection to ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:43:25Z" - latency: 8.4925ms message: 'load-balancer-api-internal: resolved host name ab79365fde25043fb9e6df496745a154-a7d29f37bbcf6c7e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:43:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:11:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-0-to-network-check-target-ip-10-0-133-91 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-0.ec2.internal uid: a4891cc0-fe0e-4201-8290-8d455b56aec2 resourceVersion: "56348" uid: 95d59ea4-7a90-42fa-b1d8-65ed669b8e2c spec: sourcePod: network-check-source-869dcfcdcd-msxnv targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T16:18:25Z" message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.368815ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:46:25Z" - latency: 2.215537ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:45:25Z" - latency: 2.088818ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:44:25Z" - latency: 2.27545ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:43:25Z" - latency: 2.525135ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:42:25Z" - latency: 2.437585ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:41:25Z" - latency: 2.472306ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:40:25Z" - latency: 2.5819ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:39:25Z" - latency: 2.417627ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:38:25Z" - latency: 2.368679ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:37:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:11:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-0-to-network-check-target-ip-10-0-135-44 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-0.ec2.internal uid: a4891cc0-fe0e-4201-8290-8d455b56aec2 resourceVersion: "56347" uid: b7ba09aa-282b-4e7a-b306-b317854d7a13 spec: sourcePod: network-check-source-869dcfcdcd-msxnv targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T16:18:25Z" message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.420585ms message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:46:25Z" - latency: 2.521389ms message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:45:25Z" - latency: 2.34833ms message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:44:25Z" - latency: 2.488547ms message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:43:25Z" - latency: 2.504523ms message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:42:25Z" - latency: 2.373389ms message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:41:25Z" - latency: 2.414444ms message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:40:25Z" - latency: 2.422088ms message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:39:25Z" - latency: 2.362691ms message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:38:25Z" - latency: 2.342056ms message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:37:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:11:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-0-to-network-check-target-ip-10-0-136-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-0.ec2.internal uid: a4891cc0-fe0e-4201-8290-8d455b56aec2 resourceVersion: "56346" uid: c66c1c41-2473-465a-a503-c94ed37482d0 spec: sourcePod: network-check-source-869dcfcdcd-msxnv targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T16:18:25Z" message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 945.104µs message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:46:25Z" - latency: 961.688µs message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:45:25Z" - latency: 907.171µs message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:44:25Z" - latency: 1.37965ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:43:25Z" - latency: 860.585µs message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:42:25Z" - latency: 973.253µs message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:41:25Z" - latency: 1.66071ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:40:25Z" - latency: 1.441305ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:39:25Z" - latency: 963.535µs message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:38:25Z" - latency: 871.175µs message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:37:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:11:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-0-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-0.ec2.internal uid: a4891cc0-fe0e-4201-8290-8d455b56aec2 resourceVersion: "57387" uid: daa3e938-07c8-4001-b6f4-08f3a6281932 spec: sourcePod: network-check-source-869dcfcdcd-msxnv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T16:17:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 872.556µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:47:25Z" - latency: 1.792248ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T16:47:25Z" - latency: 1.035024ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:46:25Z" - latency: 1.888327ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T16:46:25Z" - latency: 868.981µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:45:25Z" - latency: 1.893624ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T16:45:25Z" - latency: 936.684µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:44:25Z" - latency: 1.98854ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T16:44:25Z" - latency: 937.759µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:43:25Z" - latency: 1.934669ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T16:43:25Z" kind: List metadata: resourceVersion: ""