apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T20:50:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-219-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-219.ec2.internal uid: d9b8db87-fd5a-41d3-bd6b-fc9e6f720859 resourceVersion: "97453" uid: 9948b27b-0359-41fb-866c-89428ec1d3a2 spec: sourcePod: network-check-source-56499946bc-86srq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-01T20:57:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.711614ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:28:33Z" - latency: 993.89µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:27:33Z" - latency: 1.056569ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:26:33Z" - latency: 987.912µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:25:33Z" - latency: 985.483µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:24:33Z" - latency: 1.082512ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:23:33Z" - latency: 908.754µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:22:33Z" - latency: 1.100012ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:21:33Z" - latency: 1.115574ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:20:33Z" - latency: 1.170909ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:19:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T20:50:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-219-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-219.ec2.internal uid: d9b8db87-fd5a-41d3-bd6b-fc9e6f720859 resourceVersion: "100228" uid: 82958eb7-deee-4b40-b2e5-4ff1e1b1e97a spec: sourcePod: network-check-source-56499946bc-86srq targetEndpoint: a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T20:56:33Z" message: 'load-balancer-api-external: tcp connection to a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.228942ms message: 'load-balancer-api-external: tcp connection to a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:32:33Z" - latency: 8.322279ms message: 'load-balancer-api-external: resolved host name a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T22:32:33Z" - latency: 5.386942ms message: 'load-balancer-api-external: tcp connection to a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:31:33Z" - latency: 8.717975ms message: 'load-balancer-api-external: resolved host name a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T22:31:33Z" - latency: 4.851728ms message: 'load-balancer-api-external: tcp connection to a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:30:33Z" - latency: 9.707061ms message: 'load-balancer-api-external: resolved host name a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T22:30:33Z" - latency: 4.366034ms message: 'load-balancer-api-external: tcp connection to a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:29:33Z" - latency: 8.174135ms message: 'load-balancer-api-external: resolved host name a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T22:29:33Z" - latency: 5.427789ms message: 'load-balancer-api-external: tcp connection to a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:28:33Z" - latency: 8.408599ms message: 'load-balancer-api-external: resolved host name a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T22:28:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T20:50:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-219-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-219.ec2.internal uid: d9b8db87-fd5a-41d3-bd6b-fc9e6f720859 resourceVersion: "100229" uid: e3294723-c6b8-4b28-8878-a1ecd32e2382 spec: sourcePod: network-check-source-56499946bc-86srq targetEndpoint: a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T20:56:33Z" message: 'load-balancer-api-internal: tcp connection to a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.876495ms message: 'load-balancer-api-internal: tcp connection to a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:32:33Z" - latency: 8.495444ms message: 'load-balancer-api-internal: resolved host name a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T22:32:33Z" - latency: 4.728793ms message: 'load-balancer-api-internal: tcp connection to a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:31:33Z" - latency: 8.792641ms message: 'load-balancer-api-internal: resolved host name a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T22:31:33Z" - latency: 4.768655ms message: 'load-balancer-api-internal: tcp connection to a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:30:33Z" - latency: 9.758754ms message: 'load-balancer-api-internal: resolved host name a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T22:30:33Z" - latency: 5.337271ms message: 'load-balancer-api-internal: tcp connection to a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:29:33Z" - latency: 8.277617ms message: 'load-balancer-api-internal: resolved host name a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T22:29:33Z" - latency: 5.402749ms message: 'load-balancer-api-internal: tcp connection to a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:28:33Z" - latency: 8.363211ms message: 'load-balancer-api-internal: resolved host name a598157d2c94f4659a8dcc831855073a-75975bfcf6c3c9ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T22:28:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T20:50:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-219-to-network-check-target-ip-10-0-132-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-219.ec2.internal uid: d9b8db87-fd5a-41d3-bd6b-fc9e6f720859 resourceVersion: "97452" uid: 7f90c13e-56b7-42a3-a60f-3b5f33f87c3c spec: sourcePod: network-check-source-56499946bc-86srq targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-01T20:57:33Z" message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.463662ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:28:33Z" - latency: 2.109493ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:27:33Z" - latency: 2.20662ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:26:33Z" - latency: 2.209451ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:25:33Z" - latency: 2.35159ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:24:33Z" - latency: 2.124489ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:23:33Z" - latency: 2.188898ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:22:33Z" - latency: 2.09758ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:21:33Z" - latency: 2.129708ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:20:33Z" - latency: 2.094523ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:19:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T20:50:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-219-to-network-check-target-ip-10-0-138-219 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-219.ec2.internal uid: d9b8db87-fd5a-41d3-bd6b-fc9e6f720859 resourceVersion: "97451" uid: 97dcb957-6b2c-4014-b4c7-ce5eb449e773 spec: sourcePod: network-check-source-56499946bc-86srq targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-01T20:57:33Z" message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 645.013µs message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:28:33Z" - latency: 786.075µs message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:27:33Z" - latency: 730.43µs message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:26:33Z" - latency: 849.889µs message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:25:33Z" - latency: 716.555µs message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:24:33Z" - latency: 1.560254ms message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:23:33Z" - latency: 712.33µs message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:22:33Z" - latency: 775.336µs message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:21:33Z" - latency: 819.454µs message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:20:33Z" - latency: 1.359331ms message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:19:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T20:50:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-219-to-network-check-target-ip-10-0-140-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-219.ec2.internal uid: d9b8db87-fd5a-41d3-bd6b-fc9e6f720859 resourceVersion: "97450" uid: e9f7c38b-3f7e-441c-aa02-32a7c1291ce0 spec: sourcePod: network-check-source-56499946bc-86srq targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-01T20:57:33Z" message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.465828ms message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:28:33Z" - latency: 1.462126ms message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:27:33Z" - latency: 1.682209ms message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:26:33Z" - latency: 1.761185ms message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:25:33Z" - latency: 1.621246ms message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:24:33Z" - latency: 1.672813ms message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:23:33Z" - latency: 1.304563ms message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:22:33Z" - latency: 1.503747ms message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:21:33Z" - latency: 1.73463ms message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:20:33Z" - latency: 1.750651ms message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:19:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T20:50:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-219-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-219.ec2.internal uid: d9b8db87-fd5a-41d3-bd6b-fc9e6f720859 resourceVersion: "100227" uid: 3a13f46a-31cc-4406-a3cb-42858fde76aa spec: sourcePod: network-check-source-56499946bc-86srq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-01T20:56:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 796.708µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:32:33Z" - latency: 1.629019ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T22:32:33Z" - latency: 947.907µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:31:33Z" - latency: 1.73619ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T22:31:33Z" - latency: 743.554µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:30:33Z" - latency: 1.688833ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T22:30:33Z" - latency: 882.651µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:29:33Z" - latency: 1.723488ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T22:29:33Z" - latency: 994.257µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T22:28:33Z" - latency: 1.955825ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T22:28:33Z" kind: List metadata: resourceVersion: ""