apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:03:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-18-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-18.us-west-1.compute.internal uid: 51ae5384-7035-46b3-97f5-914c77fe74c9 resourceVersion: "23872" uid: 6d31dea6-2669-4da5-8d5f-7a29465cf467 spec: sourcePod: network-check-source-6f78d59f99-d6zcn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T09:10:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 614.441µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:45:11Z" - latency: 608.456µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:44:11Z" - latency: 606.606µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:43:11Z" - latency: 652.764µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:42:11Z" - latency: 600.141µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:41:11Z" - latency: 691.602µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:40:11Z" - latency: 584.005µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:39:11Z" - latency: 752.156µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:38:11Z" - latency: 669.907µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:37:11Z" - latency: 750.72µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:36:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:03:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-18-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-18.us-west-1.compute.internal uid: 51ae5384-7035-46b3-97f5-914c77fe74c9 resourceVersion: "23873" uid: e88309a8-aa86-4d48-8a2b-fc85b83d72e0 spec: sourcePod: network-check-source-6f78d59f99-d6zcn targetEndpoint: a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T09:09:11Z" message: 'load-balancer-api-external: tcp connection to a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.303801ms message: 'load-balancer-api-external: tcp connection to a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:45:11Z" - latency: 4.213156ms message: 'load-balancer-api-external: resolved host name a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T09:45:11Z" - latency: 63.791714ms message: 'load-balancer-api-external: tcp connection to a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:44:11Z" - latency: 4.264559ms message: 'load-balancer-api-external: resolved host name a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T09:44:11Z" - latency: 53.426569ms message: 'load-balancer-api-external: tcp connection to a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:43:11Z" - latency: 3.105088ms message: 'load-balancer-api-external: resolved host name a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T09:43:11Z" - latency: 53.617381ms message: 'load-balancer-api-external: tcp connection to a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:42:11Z" - latency: 1.700204ms message: 'load-balancer-api-external: resolved host name a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T09:42:11Z" - latency: 54.481456ms message: 'load-balancer-api-external: tcp connection to a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:41:11Z" - latency: 3.785526ms message: 'load-balancer-api-external: resolved host name a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T09:41:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:03:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-18-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-18.us-west-1.compute.internal uid: 51ae5384-7035-46b3-97f5-914c77fe74c9 resourceVersion: "23874" uid: 957c2862-6185-496f-b5dc-05493b370530 spec: sourcePod: network-check-source-6f78d59f99-d6zcn targetEndpoint: a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T09:09:11Z" message: 'load-balancer-api-internal: tcp connection to a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.750406ms message: 'load-balancer-api-internal: tcp connection to a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:45:11Z" - latency: 8.088146ms message: 'load-balancer-api-internal: resolved host name a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T09:45:11Z" - latency: 63.780998ms message: 'load-balancer-api-internal: tcp connection to a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:44:11Z" - latency: 9.092211ms message: 'load-balancer-api-internal: resolved host name a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T09:44:11Z" - latency: 53.158466ms message: 'load-balancer-api-internal: tcp connection to a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:43:11Z" - latency: 6.611996ms message: 'load-balancer-api-internal: resolved host name a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T09:43:11Z" - latency: 56.385133ms message: 'load-balancer-api-internal: tcp connection to a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:42:11Z" - latency: 5.942185ms message: 'load-balancer-api-internal: resolved host name a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T09:42:11Z" - latency: 54.489722ms message: 'load-balancer-api-internal: tcp connection to a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:41:11Z" - latency: 8.111758ms message: 'load-balancer-api-internal: resolved host name a8f4559241d9f43dcbf2f32a1af531f4-818d2f793091b729.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T09:41:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:03:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-18-to-network-check-target-ip-10-0-129-18 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-18.us-west-1.compute.internal uid: 51ae5384-7035-46b3-97f5-914c77fe74c9 resourceVersion: "23868" uid: cd9beb1c-d4bc-4270-a414-99d7e662f59f spec: sourcePod: network-check-source-6f78d59f99-d6zcn targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T09:10:11Z" message: 'network-check-target-ip-10-0-129-18: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 886.212µs message: 'network-check-target-ip-10-0-129-18: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:45:11Z" - latency: 923.459µs message: 'network-check-target-ip-10-0-129-18: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:44:11Z" - latency: 1.217204ms message: 'network-check-target-ip-10-0-129-18: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:43:11Z" - latency: 1.259128ms message: 'network-check-target-ip-10-0-129-18: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:42:11Z" - latency: 1.54478ms message: 'network-check-target-ip-10-0-129-18: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:41:11Z" - latency: 1.146737ms message: 'network-check-target-ip-10-0-129-18: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:40:11Z" - latency: 989.805µs message: 'network-check-target-ip-10-0-129-18: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:39:11Z" - latency: 940.747µs message: 'network-check-target-ip-10-0-129-18: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:38:11Z" - latency: 1.647965ms message: 'network-check-target-ip-10-0-129-18: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:37:11Z" - latency: 1.264398ms message: 'network-check-target-ip-10-0-129-18: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:36:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:03:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-18-to-network-check-target-ip-10-0-130-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-18.us-west-1.compute.internal uid: 51ae5384-7035-46b3-97f5-914c77fe74c9 resourceVersion: "23869" uid: c3c0f240-a7c5-4b9c-9b96-b652b374e63a spec: sourcePod: network-check-source-6f78d59f99-d6zcn targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T09:10:11Z" message: 'network-check-target-ip-10-0-130-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.215113ms message: 'network-check-target-ip-10-0-130-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:45:11Z" - latency: 2.16086ms message: 'network-check-target-ip-10-0-130-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:44:11Z" - latency: 2.14713ms message: 'network-check-target-ip-10-0-130-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:43:11Z" - latency: 1.993772ms message: 'network-check-target-ip-10-0-130-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:42:11Z" - latency: 2.491586ms message: 'network-check-target-ip-10-0-130-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:41:11Z" - latency: 1.872624ms message: 'network-check-target-ip-10-0-130-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:40:11Z" - latency: 2.258784ms message: 'network-check-target-ip-10-0-130-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:39:11Z" - latency: 2.339618ms message: 'network-check-target-ip-10-0-130-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:38:11Z" - latency: 2.113449ms message: 'network-check-target-ip-10-0-130-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:37:11Z" - latency: 2.149146ms message: 'network-check-target-ip-10-0-130-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:36:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:03:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-18-to-network-check-target-ip-10-0-135-30 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-18.us-west-1.compute.internal uid: 51ae5384-7035-46b3-97f5-914c77fe74c9 resourceVersion: "23870" uid: 0fe8a84d-7b33-4482-b9ea-1726890199b0 spec: sourcePod: network-check-source-6f78d59f99-d6zcn targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T09:10:11Z" message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.189514ms message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:45:11Z" - latency: 1.976421ms message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:44:11Z" - latency: 1.813672ms message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:43:11Z" - latency: 1.887956ms message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:42:11Z" - latency: 1.930239ms message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:41:11Z" - latency: 2.157637ms message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:40:11Z" - latency: 2.31028ms message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:39:11Z" - latency: 2.307137ms message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:38:11Z" - latency: 2.463963ms message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:37:11Z" - latency: 1.801661ms message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:36:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:03:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-18-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-18.us-west-1.compute.internal uid: 51ae5384-7035-46b3-97f5-914c77fe74c9 resourceVersion: "23871" uid: 5b8cae28-13b9-429f-87e8-18e2c02ff25c spec: sourcePod: network-check-source-6f78d59f99-d6zcn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T09:09:11Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 731.611µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:45:11Z" - latency: 2.179963ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T09:45:11Z" - latency: 1.147482ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:44:11Z" - latency: 1.789732ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T09:44:11Z" - latency: 991.972µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:43:11Z" - latency: 1.562517ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T09:43:11Z" - latency: 873.92µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:42:11Z" - latency: 1.686853ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T09:42:11Z" - latency: 844.326µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:41:11Z" - latency: 1.783606ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T09:41:11Z" kind: List metadata: resourceVersion: ""