apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:43:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-151-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-151.us-west-2.compute.internal uid: d86c5f7d-000d-457d-a5c5-fc251f9e68f9 resourceVersion: "36023" uid: 877c3974-1b9c-41c6-92e6-041cf3d8e80e spec: sourcePod: network-check-source-6f78d59f99-tfx5k targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-04T02:50:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.173931ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:07:54Z" - latency: 1.254617ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:06:54Z" - latency: 1.364166ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:05:54Z" - latency: 1.193273ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:04:54Z" - latency: 757.083µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:03:54Z" - latency: 1.633826ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:02:54Z" - latency: 1.594698ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:01:54Z" - latency: 1.055765ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:00:54Z" - latency: 1.201715ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:59:54Z" - latency: 1.643118ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:58:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:43:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-151-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-151.us-west-2.compute.internal uid: d86c5f7d-000d-457d-a5c5-fc251f9e68f9 resourceVersion: "36024" uid: 380f7dc8-dd12-471f-8ba4-9fc79c0fc367 spec: sourcePod: network-check-source-6f78d59f99-tfx5k targetEndpoint: ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T02:49:54Z" message: 'load-balancer-api-external: tcp connection to ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.863734ms message: 'load-balancer-api-external: tcp connection to ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:07:54Z" - latency: 7.794137ms message: 'load-balancer-api-external: resolved host name ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:07:54Z" - latency: 54.881901ms message: 'load-balancer-api-external: tcp connection to ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:06:54Z" - latency: 8.216607ms message: 'load-balancer-api-external: resolved host name ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:06:54Z" - latency: 55.131883ms message: 'load-balancer-api-external: tcp connection to ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:05:54Z" - latency: 8.649534ms message: 'load-balancer-api-external: resolved host name ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:05:54Z" - latency: 57.062614ms message: 'load-balancer-api-external: tcp connection to ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:04:54Z" - latency: 6.924757ms message: 'load-balancer-api-external: resolved host name ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:04:54Z" - latency: 102.219396ms message: 'load-balancer-api-external: tcp connection to ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:03:54Z" - latency: 9.495653ms message: 'load-balancer-api-external: resolved host name ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:03:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:43:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-151-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-151.us-west-2.compute.internal uid: d86c5f7d-000d-457d-a5c5-fc251f9e68f9 resourceVersion: "36025" uid: c47c0300-777e-41a1-b8c3-16f846461ccc spec: sourcePod: network-check-source-6f78d59f99-tfx5k targetEndpoint: ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T02:49:54Z" message: 'load-balancer-api-internal: tcp connection to ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.634054ms message: 'load-balancer-api-internal: tcp connection to ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:07:54Z" - latency: 7.828452ms message: 'load-balancer-api-internal: resolved host name ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:07:54Z" - latency: 54.60025ms message: 'load-balancer-api-internal: tcp connection to ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:06:54Z" - latency: 8.233027ms message: 'load-balancer-api-internal: resolved host name ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:06:54Z" - latency: 54.201657ms message: 'load-balancer-api-internal: tcp connection to ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:05:54Z" - latency: 8.720374ms message: 'load-balancer-api-internal: resolved host name ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:05:54Z" - latency: 56.06764ms message: 'load-balancer-api-internal: tcp connection to ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:04:54Z" - latency: 6.996329ms message: 'load-balancer-api-internal: resolved host name ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:04:54Z" - latency: 52.545791ms message: 'load-balancer-api-internal: tcp connection to ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:03:54Z" - latency: 9.614735ms message: 'load-balancer-api-internal: resolved host name ae14357e01c2f4bb980c683cef2a7487-ed877d226064731f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:03:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:43:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-151-to-network-check-target-ip-10-0-130-151 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-151.us-west-2.compute.internal uid: d86c5f7d-000d-457d-a5c5-fc251f9e68f9 resourceVersion: "36019" uid: 3b9cc0bf-091b-439d-a6d8-b10f9469f272 spec: sourcePod: network-check-source-6f78d59f99-tfx5k targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T02:50:54Z" message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 883.518µs message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:07:54Z" - latency: 909.638µs message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:06:54Z" - latency: 1.469754ms message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:05:54Z" - latency: 1.329159ms message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:04:54Z" - latency: 1.481453ms message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:03:54Z" - latency: 1.418066ms message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:02:54Z" - latency: 919.737µs message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:01:54Z" - latency: 1.68725ms message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:00:54Z" - latency: 1.028687ms message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:59:54Z" - latency: 980.266µs message: 'network-check-target-ip-10-0-130-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:58:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:43:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-151-to-network-check-target-ip-10-0-132-179 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-151.us-west-2.compute.internal uid: d86c5f7d-000d-457d-a5c5-fc251f9e68f9 resourceVersion: "36021" uid: 7eee3d51-42d5-43cc-a4fd-ee6d8be039e2 spec: sourcePod: network-check-source-6f78d59f99-tfx5k targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T02:50:54Z" message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.631656ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:07:54Z" - latency: 2.303145ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:06:54Z" - latency: 2.131876ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:05:54Z" - latency: 2.153041ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:04:54Z" - latency: 1.921965ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:03:54Z" - latency: 2.400582ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:02:54Z" - latency: 2.252574ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:01:54Z" - latency: 2.205127ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:00:54Z" - latency: 2.253664ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:59:54Z" - latency: 2.636222ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:58:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:43:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-151-to-network-check-target-ip-10-0-137-184 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-151.us-west-2.compute.internal uid: d86c5f7d-000d-457d-a5c5-fc251f9e68f9 resourceVersion: "36020" uid: 7aef56df-5f07-4c57-bd8a-a06013ecf274 spec: sourcePod: network-check-source-6f78d59f99-tfx5k targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-04T02:50:54Z" message: 'network-check-target-ip-10-0-137-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.50882ms message: 'network-check-target-ip-10-0-137-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:07:54Z" - latency: 2.151319ms message: 'network-check-target-ip-10-0-137-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:06:54Z" - latency: 2.196943ms message: 'network-check-target-ip-10-0-137-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:05:54Z" - latency: 2.097043ms message: 'network-check-target-ip-10-0-137-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:04:54Z" - latency: 1.830554ms message: 'network-check-target-ip-10-0-137-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:03:54Z" - latency: 2.209113ms message: 'network-check-target-ip-10-0-137-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:02:54Z" - latency: 2.08121ms message: 'network-check-target-ip-10-0-137-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:01:54Z" - latency: 2.182627ms message: 'network-check-target-ip-10-0-137-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:00:54Z" - latency: 2.091186ms message: 'network-check-target-ip-10-0-137-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:59:54Z" - latency: 2.031939ms message: 'network-check-target-ip-10-0-137-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:58:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:43:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-151-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-151.us-west-2.compute.internal uid: d86c5f7d-000d-457d-a5c5-fc251f9e68f9 resourceVersion: "36022" uid: 2886457b-3c93-4737-a201-a07de7376dbb spec: sourcePod: network-check-source-6f78d59f99-tfx5k targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-04T02:49:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.023421ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:07:54Z" - latency: 2.120437ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T04:07:54Z" - latency: 889.947µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:06:54Z" - latency: 2.280792ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T04:06:54Z" - latency: 1.03582ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:05:54Z" - latency: 2.135753ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T04:05:54Z" - latency: 1.008233ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:04:54Z" - latency: 2.215282ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T04:04:54Z" - latency: 761.972µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:03:54Z" - latency: 2.208012ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T04:03:54Z" kind: List metadata: resourceVersion: ""