apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:21:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-158-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-158.ec2.internal uid: 13746775-ae66-4e7b-be7d-9a674621ddbf resourceVersion: "51551" uid: 436a37ae-e0d5-4942-a647-646fc8d9bfc1 spec: sourcePod: network-check-source-989f8b8dc-spd4h targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T18:28:50Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.190591ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:56:50Z" - latency: 946.058µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:55:50Z" - latency: 900.937µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:54:50Z" - latency: 1.208982ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:53:50Z" - latency: 1.089626ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:52:50Z" - latency: 972.602µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:51:50Z" - latency: 1.208808ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:50:50Z" - latency: 877.54µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:49:50Z" - latency: 888.701µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:48:50Z" - latency: 700.111µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:47:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:21:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-158-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-158.ec2.internal uid: 13746775-ae66-4e7b-be7d-9a674621ddbf resourceVersion: "52154" uid: 4500b2eb-4122-4611-8996-c5e5ebe44691 spec: sourcePod: network-check-source-989f8b8dc-spd4h targetEndpoint: a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T18:27:50Z" message: 'load-balancer-api-external: tcp connection to a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.311742ms message: 'load-balancer-api-external: tcp connection to a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:57:50Z" - latency: 7.47636ms message: 'load-balancer-api-external: resolved host name a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:57:50Z" - latency: 5.420172ms message: 'load-balancer-api-external: tcp connection to a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:56:50Z" - latency: 6.953766ms message: 'load-balancer-api-external: resolved host name a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:56:50Z" - latency: 3.458319ms message: 'load-balancer-api-external: tcp connection to a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:55:50Z" - latency: 6.802892ms message: 'load-balancer-api-external: resolved host name a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:55:50Z" - latency: 3.87942ms message: 'load-balancer-api-external: tcp connection to a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:54:50Z" - latency: 6.770317ms message: 'load-balancer-api-external: resolved host name a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:54:50Z" - latency: 5.211884ms message: 'load-balancer-api-external: tcp connection to a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:53:50Z" - latency: 8.386249ms message: 'load-balancer-api-external: resolved host name a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:53:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:21:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-158-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-158.ec2.internal uid: 13746775-ae66-4e7b-be7d-9a674621ddbf resourceVersion: "52155" uid: 066498c0-ea6f-467b-b74f-a18bab593770 spec: sourcePod: network-check-source-989f8b8dc-spd4h targetEndpoint: a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T18:27:50Z" message: 'load-balancer-api-internal: tcp connection to a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.29134ms message: 'load-balancer-api-internal: tcp connection to a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:57:50Z" - latency: 7.589516ms message: 'load-balancer-api-internal: resolved host name a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:57:50Z" - latency: 5.411962ms message: 'load-balancer-api-internal: tcp connection to a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:56:50Z" - latency: 7.103497ms message: 'load-balancer-api-internal: resolved host name a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:56:50Z" - latency: 3.478374ms message: 'load-balancer-api-internal: tcp connection to a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:55:50Z" - latency: 6.890333ms message: 'load-balancer-api-internal: resolved host name a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:55:50Z" - latency: 3.942486ms message: 'load-balancer-api-internal: tcp connection to a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:54:50Z" - latency: 6.888139ms message: 'load-balancer-api-internal: resolved host name a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:54:50Z" - latency: 3.802478ms message: 'load-balancer-api-internal: tcp connection to a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:53:50Z" - latency: 8.408006ms message: 'load-balancer-api-internal: resolved host name a2bd975b1c5b346d1861e3e4dca0f6c7-93f778be5dbc83b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:53:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:21:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-158-to-network-check-target-ip-10-0-130-158 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-158.ec2.internal uid: 13746775-ae66-4e7b-be7d-9a674621ddbf resourceVersion: "51548" uid: 9f737fe7-08b6-430e-a921-1d9f3eeb4c3d spec: sourcePod: network-check-source-989f8b8dc-spd4h targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T18:28:50Z" message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 996.256µs message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:56:50Z" - latency: 1.113771ms message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:55:50Z" - latency: 970.464µs message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:54:50Z" - latency: 1.02304ms message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:53:50Z" - latency: 1.025228ms message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:52:50Z" - latency: 890.202µs message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:51:50Z" - latency: 1.400388ms message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:50:50Z" - latency: 1.088107ms message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:49:50Z" - latency: 949.504µs message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:48:50Z" - latency: 1.047296ms message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:47:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:21:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-158-to-network-check-target-ip-10-0-130-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-158.ec2.internal uid: 13746775-ae66-4e7b-be7d-9a674621ddbf resourceVersion: "51550" uid: 13b1f741-1fcf-4289-92d1-e4791b392a29 spec: sourcePod: network-check-source-989f8b8dc-spd4h targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T18:28:50Z" message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.515786ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:56:50Z" - latency: 2.272893ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:55:50Z" - latency: 2.386362ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:54:50Z" - latency: 2.228771ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:53:50Z" - latency: 2.345413ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:52:50Z" - latency: 2.313266ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:51:50Z" - latency: 2.18023ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:50:50Z" - latency: 2.107471ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:49:50Z" - latency: 2.503144ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:48:50Z" - latency: 2.163801ms message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:47:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:21:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-158-to-network-check-target-ip-10-0-138-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-158.ec2.internal uid: 13746775-ae66-4e7b-be7d-9a674621ddbf resourceVersion: "51549" uid: 0361b501-1720-486a-a765-f778b7de5d49 spec: sourcePod: network-check-source-989f8b8dc-spd4h targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T18:28:50Z" message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.133656ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:56:50Z" - latency: 2.058843ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:55:50Z" - latency: 2.311716ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:54:50Z" - latency: 2.463161ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:53:50Z" - latency: 2.590206ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:52:50Z" - latency: 2.463506ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:51:50Z" - latency: 2.473643ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:50:50Z" - latency: 2.226128ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:49:50Z" - latency: 2.613975ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:48:50Z" - latency: 2.119686ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:47:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:21:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-158-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-158.ec2.internal uid: 13746775-ae66-4e7b-be7d-9a674621ddbf resourceVersion: "52153" uid: 39626628-fa18-48e4-a253-71b144ebe654 spec: sourcePod: network-check-source-989f8b8dc-spd4h targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T18:27:50Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 841.83µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:57:50Z" - latency: 2.440455ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:57:50Z" - latency: 1.240588ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:56:50Z" - latency: 1.783178ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:56:50Z" - latency: 968.215µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:55:50Z" - latency: 1.803901ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:55:50Z" - latency: 979.48µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:54:50Z" - latency: 1.963748ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:54:50Z" - latency: 775.114µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:53:50Z" - latency: 2.408982ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:53:50Z" kind: List metadata: resourceVersion: ""