apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:29:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-22-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-22.ec2.internal uid: 91eae0d7-1f3d-44c1-abdf-a5a36f3fefd8 resourceVersion: "49162" uid: 45f8bfe8-67ff-4215-b34b-dfaf77d96d09 spec: sourcePod: network-check-source-7bc5b6bf85-l5q5z targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-21T17:36:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.136814ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:46:15Z" - latency: 931.845µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:45:15Z" - latency: 995.82µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:44:15Z" - latency: 1.277944ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:43:15Z" - latency: 1.071849ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:42:15Z" - latency: 996.686µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:41:15Z" - latency: 799.397µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:40:15Z" - latency: 1.177089ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:39:15Z" - latency: 859.714µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:38:15Z" - latency: 861.824µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:37:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:29:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-22-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-22.ec2.internal uid: 91eae0d7-1f3d-44c1-abdf-a5a36f3fefd8 resourceVersion: "49770" uid: f8462910-eddc-4535-b03f-ac895e99f711 spec: sourcePod: network-check-source-7bc5b6bf85-l5q5z targetEndpoint: a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T17:35:15Z" message: 'load-balancer-api-external: tcp connection to a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.655267ms message: 'load-balancer-api-external: tcp connection to a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:47:15Z" - latency: 8.23287ms message: 'load-balancer-api-external: resolved host name a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T18:47:15Z" - latency: 4.686275ms message: 'load-balancer-api-external: tcp connection to a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:46:15Z" - latency: 8.094662ms message: 'load-balancer-api-external: resolved host name a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T18:46:15Z" - latency: 4.656866ms message: 'load-balancer-api-external: tcp connection to a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:45:15Z" - latency: 8.489608ms message: 'load-balancer-api-external: resolved host name a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T18:45:15Z" - latency: 4.796028ms message: 'load-balancer-api-external: tcp connection to a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:44:15Z" - latency: 8.328045ms message: 'load-balancer-api-external: resolved host name a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T18:44:15Z" - latency: 4.638412ms message: 'load-balancer-api-external: tcp connection to a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:43:15Z" - latency: 8.704015ms message: 'load-balancer-api-external: resolved host name a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T18:43:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:29:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-22-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-22.ec2.internal uid: 91eae0d7-1f3d-44c1-abdf-a5a36f3fefd8 resourceVersion: "49771" uid: cf4dbe49-e8c2-4d30-8264-44fb6b780dcf spec: sourcePod: network-check-source-7bc5b6bf85-l5q5z targetEndpoint: a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T17:35:15Z" message: 'load-balancer-api-internal: tcp connection to a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.035625ms message: 'load-balancer-api-internal: tcp connection to a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:47:15Z" - latency: 8.356974ms message: 'load-balancer-api-internal: resolved host name a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T18:47:15Z" - latency: 4.184562ms message: 'load-balancer-api-internal: tcp connection to a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:46:15Z" - latency: 8.200936ms message: 'load-balancer-api-internal: resolved host name a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T18:46:15Z" - latency: 4.671149ms message: 'load-balancer-api-internal: tcp connection to a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:45:15Z" - latency: 8.442868ms message: 'load-balancer-api-internal: resolved host name a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T18:45:15Z" - latency: 4.771078ms message: 'load-balancer-api-internal: tcp connection to a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:44:15Z" - latency: 8.419491ms message: 'load-balancer-api-internal: resolved host name a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T18:44:15Z" - latency: 4.873763ms message: 'load-balancer-api-internal: tcp connection to a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:43:15Z" - latency: 8.775727ms message: 'load-balancer-api-internal: resolved host name a62f01acf67534245b964def70c36ec1-5530025c2b7c2193.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T18:43:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:29:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-22-to-network-check-target-ip-10-0-129-22 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-22.ec2.internal uid: 91eae0d7-1f3d-44c1-abdf-a5a36f3fefd8 resourceVersion: "49159" uid: c4c52c19-1474-4118-9d25-73edcaf5a821 spec: sourcePod: network-check-source-7bc5b6bf85-l5q5z targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T17:36:15Z" message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 830.283µs message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:46:15Z" - latency: 1.431249ms message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:45:15Z" - latency: 1.203147ms message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:44:15Z" - latency: 910.346µs message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:43:15Z" - latency: 1.418193ms message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:42:15Z" - latency: 917.952µs message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:41:15Z" - latency: 906.883µs message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:40:15Z" - latency: 1.09373ms message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:39:15Z" - latency: 842.545µs message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:38:15Z" - latency: 1.274665ms message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:37:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:29:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-22-to-network-check-target-ip-10-0-135-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-22.ec2.internal uid: 91eae0d7-1f3d-44c1-abdf-a5a36f3fefd8 resourceVersion: "49161" uid: 3dd05aa8-3acb-4eab-a382-339320c1c746 spec: sourcePod: network-check-source-7bc5b6bf85-l5q5z targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T17:36:15Z" message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.070804ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:46:15Z" - latency: 2.17611ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:45:15Z" - latency: 2.338409ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:44:15Z" - latency: 2.363278ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:43:15Z" - latency: 1.971829ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:42:15Z" - latency: 2.362069ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:41:15Z" - latency: 2.372088ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:40:15Z" - latency: 2.213662ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:39:15Z" - latency: 2.19181ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:38:15Z" - latency: 2.063076ms message: 'network-check-target-ip-10-0-135-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:37:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:29:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-22-to-network-check-target-ip-10-0-136-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-22.ec2.internal uid: 91eae0d7-1f3d-44c1-abdf-a5a36f3fefd8 resourceVersion: "49160" uid: ed798d7f-0353-41c0-9e4e-b78af26a4935 spec: sourcePod: network-check-source-7bc5b6bf85-l5q5z targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-21T17:36:15Z" message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.169733ms message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:46:15Z" - latency: 2.326965ms message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:45:15Z" - latency: 2.338851ms message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:44:15Z" - latency: 2.290552ms message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:43:15Z" - latency: 2.28401ms message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:42:15Z" - latency: 4.752557ms message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:41:15Z" - latency: 2.279379ms message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:40:15Z" - latency: 2.168047ms message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:39:15Z" - latency: 1.972231ms message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:38:15Z" - latency: 2.178165ms message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:37:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:29:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-22-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-22.ec2.internal uid: 91eae0d7-1f3d-44c1-abdf-a5a36f3fefd8 resourceVersion: "49769" uid: 7cd19f8f-78da-42db-a995-a25994e90b5c spec: sourcePod: network-check-source-7bc5b6bf85-l5q5z targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-21T17:35:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 893.402µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:47:15Z" - latency: 1.601043ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T18:47:15Z" - latency: 778.603µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:46:15Z" - latency: 1.631433ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T18:46:15Z" - latency: 1.123494ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:45:15Z" - latency: 1.752279ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T18:45:15Z" - latency: 977.938µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:44:15Z" - latency: 1.564702ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T18:44:15Z" - latency: 1.171995ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T18:43:15Z" - latency: 1.861451ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T18:43:15Z" kind: List metadata: resourceVersion: ""