apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:55:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-78-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-78.ec2.internal uid: b29f050e-a51f-4150-b86b-47afb1e50e51 resourceVersion: "61667" uid: b7ce9d3c-194b-4788-aad7-b8073cfa7d68 spec: sourcePod: network-check-source-869dcfcdcd-dj44p targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T12:02:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.149107ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:37:44Z" - latency: 1.107662ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:36:44Z" - latency: 1.045816ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:35:44Z" - latency: 936.781µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:34:44Z" - latency: 899.662µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:33:44Z" - latency: 1.242481ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:32:44Z" - latency: 923.47µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:31:44Z" - latency: 1.138259ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:30:44Z" - latency: 996.405µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:29:44Z" - latency: 992.491µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:28:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:55:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-78-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-78.ec2.internal uid: b29f050e-a51f-4150-b86b-47afb1e50e51 resourceVersion: "61668" uid: 37472d74-b75b-48d0-bbbf-1a5b5940d1c9 spec: sourcePod: network-check-source-869dcfcdcd-dj44p targetEndpoint: ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T12:01:44Z" message: 'load-balancer-api-external: tcp connection to ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.468057ms message: 'load-balancer-api-external: tcp connection to ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:37:44Z" - latency: 6.432716ms message: 'load-balancer-api-external: resolved host name ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:37:44Z" - latency: 5.655522ms message: 'load-balancer-api-external: tcp connection to ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:36:44Z" - latency: 6.783023ms message: 'load-balancer-api-external: resolved host name ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:36:44Z" - latency: 5.053221ms message: 'load-balancer-api-external: tcp connection to ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:35:44Z" - latency: 6.977646ms message: 'load-balancer-api-external: resolved host name ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:35:44Z" - latency: 5.207518ms message: 'load-balancer-api-external: tcp connection to ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:34:44Z" - latency: 7.309485ms message: 'load-balancer-api-external: resolved host name ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:34:44Z" - latency: 6.97891ms message: 'load-balancer-api-external: tcp connection to ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:33:44Z" - latency: 6.470101ms message: 'load-balancer-api-external: resolved host name ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:33:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:55:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-78-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-78.ec2.internal uid: b29f050e-a51f-4150-b86b-47afb1e50e51 resourceVersion: "61669" uid: e88ba37c-0e87-40f6-a70b-b10ee8caa3a7 spec: sourcePod: network-check-source-869dcfcdcd-dj44p targetEndpoint: ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T12:01:44Z" message: 'load-balancer-api-internal: tcp connection to ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.744362ms message: 'load-balancer-api-internal: tcp connection to ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:37:44Z" - latency: 6.328758ms message: 'load-balancer-api-internal: resolved host name ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:37:44Z" - latency: 3.213046ms message: 'load-balancer-api-internal: tcp connection to ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:36:44Z" - latency: 6.636459ms message: 'load-balancer-api-internal: resolved host name ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:36:44Z" - latency: 3.698876ms message: 'load-balancer-api-internal: tcp connection to ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:35:44Z" - latency: 6.922741ms message: 'load-balancer-api-internal: resolved host name ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:35:44Z" - latency: 4.473797ms message: 'load-balancer-api-internal: tcp connection to ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:34:44Z" - latency: 7.227301ms message: 'load-balancer-api-internal: resolved host name ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:34:44Z" - latency: 3.708899ms message: 'load-balancer-api-internal: tcp connection to ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:33:44Z" - latency: 6.506069ms message: 'load-balancer-api-internal: resolved host name ae73d5924759e4a4787d141874888122-8f9ba500ee186458.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:33:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:55:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-78-to-network-check-target-ip-10-0-129-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-78.ec2.internal uid: b29f050e-a51f-4150-b86b-47afb1e50e51 resourceVersion: "61664" uid: 39bd89bb-6868-4f0c-b97d-0151e75483c3 spec: sourcePod: network-check-source-869dcfcdcd-dj44p targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T12:02:44Z" message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.287496ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:37:44Z" - latency: 2.6436ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:36:44Z" - latency: 2.372908ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:35:44Z" - latency: 2.050742ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:34:44Z" - latency: 2.298504ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:33:44Z" - latency: 2.266606ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:32:44Z" - latency: 2.181661ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:31:44Z" - latency: 2.107557ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:30:44Z" - latency: 2.178491ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:29:44Z" - latency: 2.491769ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:28:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:55:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-78-to-network-check-target-ip-10-0-129-78 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-78.ec2.internal uid: b29f050e-a51f-4150-b86b-47afb1e50e51 resourceVersion: "61663" uid: 574960e9-f59f-42d6-8d35-3e3ff0f7cedc spec: sourcePod: network-check-source-869dcfcdcd-dj44p targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T12:02:44Z" message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.269385ms message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:37:44Z" - latency: 847.653µs message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:36:44Z" - latency: 1.36894ms message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:35:44Z" - latency: 973.767µs message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:34:44Z" - latency: 922.845µs message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:33:44Z" - latency: 1.452932ms message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:32:44Z" - latency: 945.88µs message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:31:44Z" - latency: 1.153751ms message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:30:44Z" - latency: 797.118µs message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:29:44Z" - latency: 940.726µs message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:28:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:55:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-78-to-network-check-target-ip-10-0-137-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-78.ec2.internal uid: b29f050e-a51f-4150-b86b-47afb1e50e51 resourceVersion: "61665" uid: 6806e8c9-a4fa-4000-a85a-4fc9dc4c8562 spec: sourcePod: network-check-source-869dcfcdcd-dj44p targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T12:02:44Z" message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.251076ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:37:44Z" - latency: 2.058521ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:36:44Z" - latency: 2.14613ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:35:44Z" - latency: 1.96448ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:34:44Z" - latency: 2.100727ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:33:44Z" - latency: 1.774968ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:32:44Z" - latency: 2.233921ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:31:44Z" - latency: 1.982755ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:30:44Z" - latency: 1.820468ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:29:44Z" - latency: 2.08388ms message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:28:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:55:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-78-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-78.ec2.internal uid: b29f050e-a51f-4150-b86b-47afb1e50e51 resourceVersion: "61666" uid: b8fc6d67-c456-48bf-8518-4a5429231da0 spec: sourcePod: network-check-source-869dcfcdcd-dj44p targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T12:01:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 955.461µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:37:44Z" - latency: 1.712184ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T12:37:44Z" - latency: 933.126µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:36:44Z" - latency: 1.686906ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T12:36:44Z" - latency: 843.698µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:35:44Z" - latency: 1.723318ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T12:35:44Z" - latency: 1.130087ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:34:44Z" - latency: 1.809063ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T12:34:44Z" - latency: 883.258µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:33:44Z" - latency: 1.584385ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T12:33:44Z" kind: List metadata: resourceVersion: ""