apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:54:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: 23127619-c8ea-4323-b38b-21bf3045773c resourceVersion: "32315" uid: f13e75ee-b3c4-4dcd-9d80-f13e5b0616c1 spec: sourcePod: network-check-source-869dcfcdcd-b8h47 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-13T19:01:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 934.978µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:36:04Z" - latency: 1.182362ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:35:04Z" - latency: 1.024497ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:34:04Z" - latency: 1.015981ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:33:04Z" - latency: 1.128482ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:32:04Z" - latency: 950.971µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:31:04Z" - latency: 1.070409ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:30:04Z" - latency: 1.092735ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:29:04Z" - latency: 1.224437ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:28:04Z" - latency: 1.113526ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:27:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:54:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: 23127619-c8ea-4323-b38b-21bf3045773c resourceVersion: "32316" uid: f457d373-1207-45ad-832d-68b6b731704a spec: sourcePod: network-check-source-869dcfcdcd-b8h47 targetEndpoint: af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T19:00:04Z" message: 'load-balancer-api-external: tcp connection to af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.023759ms message: 'load-balancer-api-external: tcp connection to af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:36:04Z" - latency: 9.642237ms message: 'load-balancer-api-external: resolved host name af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:36:04Z" - latency: 4.684032ms message: 'load-balancer-api-external: tcp connection to af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:35:04Z" - latency: 9.56236ms message: 'load-balancer-api-external: resolved host name af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:35:04Z" - latency: 4.739595ms message: 'load-balancer-api-external: tcp connection to af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:34:04Z" - latency: 8.04577ms message: 'load-balancer-api-external: resolved host name af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:34:04Z" - latency: 5.654321ms message: 'load-balancer-api-external: tcp connection to af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:33:04Z" - latency: 8.663561ms message: 'load-balancer-api-external: resolved host name af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:33:04Z" - latency: 5.352081ms message: 'load-balancer-api-external: tcp connection to af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:32:04Z" - latency: 8.410126ms message: 'load-balancer-api-external: resolved host name af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:32:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:54:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: 23127619-c8ea-4323-b38b-21bf3045773c resourceVersion: "32317" uid: 06ee8a28-0b33-416f-8e1f-061164b8cf96 spec: sourcePod: network-check-source-869dcfcdcd-b8h47 targetEndpoint: af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T19:00:04Z" message: 'load-balancer-api-internal: tcp connection to af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.03062ms message: 'load-balancer-api-internal: tcp connection to af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:36:04Z" - latency: 9.599547ms message: 'load-balancer-api-internal: resolved host name af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:36:04Z" - latency: 4.655276ms message: 'load-balancer-api-internal: tcp connection to af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:35:04Z" - latency: 9.513541ms message: 'load-balancer-api-internal: resolved host name af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:35:04Z" - latency: 5.817854ms message: 'load-balancer-api-internal: tcp connection to af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:34:04Z" - latency: 8.01854ms message: 'load-balancer-api-internal: resolved host name af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:34:04Z" - latency: 5.020271ms message: 'load-balancer-api-internal: tcp connection to af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:33:04Z" - latency: 8.620649ms message: 'load-balancer-api-internal: resolved host name af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:33:04Z" - latency: 4.864573ms message: 'load-balancer-api-internal: tcp connection to af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:32:04Z" - latency: 8.358135ms message: 'load-balancer-api-internal: resolved host name af752f5f49f0a4fac9409f307976c266-71a4b248f91d0e70.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:32:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:54:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-network-check-target-ip-10-0-128-27 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: 23127619-c8ea-4323-b38b-21bf3045773c resourceVersion: "32312" uid: 6866797c-50dd-41ec-a44b-d671dd00c933 spec: sourcePod: network-check-source-869dcfcdcd-b8h47 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T19:01:04Z" message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.23428ms message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:36:04Z" - latency: 2.148639ms message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:35:04Z" - latency: 2.17149ms message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:34:04Z" - latency: 2.173491ms message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:33:04Z" - latency: 2.087782ms message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:32:04Z" - latency: 2.152828ms message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:31:04Z" - latency: 2.30015ms message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:30:04Z" - latency: 1.991129ms message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:29:04Z" - latency: 2.090695ms message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:28:04Z" - latency: 2.058045ms message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:27:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:54:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-network-check-target-ip-10-0-137-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: 23127619-c8ea-4323-b38b-21bf3045773c resourceVersion: "32314" uid: 1a9b6d60-f76d-43d1-994c-eaf4d9b72626 spec: sourcePod: network-check-source-869dcfcdcd-b8h47 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-13T19:01:04Z" message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.53302ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:36:04Z" - latency: 2.80247ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:35:04Z" - latency: 2.185018ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:34:04Z" - latency: 2.478099ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:33:04Z" - latency: 2.40988ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:32:04Z" - latency: 2.520205ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:31:04Z" - latency: 2.771091ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:30:04Z" - latency: 2.633132ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:29:04Z" - latency: 1.951993ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:28:04Z" - latency: 2.532885ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:27:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:54:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-network-check-target-ip-10-0-139-100 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: 23127619-c8ea-4323-b38b-21bf3045773c resourceVersion: "32311" uid: b35d899e-8f68-4618-938f-7bf130f545c1 spec: sourcePod: network-check-source-869dcfcdcd-b8h47 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-13T19:01:04Z" message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 928.112µs message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:36:04Z" - latency: 1.457523ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:35:04Z" - latency: 1.256637ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:34:04Z" - latency: 866.284µs message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:33:04Z" - latency: 834.469µs message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:32:04Z" - latency: 927.33µs message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:31:04Z" - latency: 1.452076ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:30:04Z" - latency: 1.293115ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:29:04Z" - latency: 921.278µs message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:28:04Z" - latency: 911.235µs message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:27:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:54:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: 23127619-c8ea-4323-b38b-21bf3045773c resourceVersion: "32313" uid: 81be2027-6db5-4063-844b-0def0b7e6c05 spec: sourcePod: network-check-source-869dcfcdcd-b8h47 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-13T19:00:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.107663ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:36:04Z" - latency: 1.686696ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T19:36:04Z" - latency: 1.621864ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:35:04Z" - latency: 1.699018ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T19:35:04Z" - latency: 1.026469ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:34:04Z" - latency: 1.803309ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T19:34:04Z" - latency: 846.831µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:33:04Z" - latency: 1.696954ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T19:33:04Z" - latency: 866.535µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:32:04Z" - latency: 1.775313ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T19:32:04Z" kind: List metadata: resourceVersion: ""