apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:03:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-6-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-6.ec2.internal uid: eb77757d-fc86-4b53-b970-49e39b76adda resourceVersion: "16498" uid: a2c44dcb-6555-4a5c-9c76-c2f3181c387a spec: sourcePod: network-check-source-7d88cb55d8-c244p targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T17:10:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.487µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:17:40Z" - latency: 922.922µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:16:40Z" - latency: 1.309354ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:15:40Z" - latency: 1.021145ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:14:40Z" - latency: 1.527422ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:13:40Z" - latency: 1.078295ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:12:40Z" - latency: 772.814µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:11:40Z" - latency: 942.258µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:10:40Z" - latency: 1.359898ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:09:40Z" - latency: 994.749µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:08:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:03:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-6-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-6.ec2.internal uid: eb77757d-fc86-4b53-b970-49e39b76adda resourceVersion: "15774" uid: d22a53ca-fcbe-495a-ae5f-2df6ad8579ce spec: sourcePod: network-check-source-7d88cb55d8-c244p targetEndpoint: aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T17:09:40Z" message: 'load-balancer-api-external: tcp connection to aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.145881ms message: 'load-balancer-api-external: tcp connection to aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:15:40Z" - latency: 6.535354ms message: 'load-balancer-api-external: resolved host name aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:15:40Z" - latency: 5.526303ms message: 'load-balancer-api-external: tcp connection to aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:14:40Z" - latency: 7.078182ms message: 'load-balancer-api-external: resolved host name aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:14:40Z" - latency: 6.134888ms message: 'load-balancer-api-external: tcp connection to aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:13:40Z" - latency: 6.967968ms message: 'load-balancer-api-external: resolved host name aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:13:40Z" - latency: 4.541669ms message: 'load-balancer-api-external: tcp connection to aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:12:40Z" - latency: 6.667013ms message: 'load-balancer-api-external: resolved host name aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:12:40Z" - latency: 4.83797ms message: 'load-balancer-api-external: tcp connection to aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:11:40Z" - latency: 7.251099ms message: 'load-balancer-api-external: resolved host name aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:11:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:03:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-6-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-6.ec2.internal uid: eb77757d-fc86-4b53-b970-49e39b76adda resourceVersion: "15773" uid: 8564c29b-e4bf-4b05-809d-60f0b90899cb spec: sourcePod: network-check-source-7d88cb55d8-c244p targetEndpoint: aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T17:09:40Z" message: 'load-balancer-api-internal: tcp connection to aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.184114ms message: 'load-balancer-api-internal: tcp connection to aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:15:40Z" - latency: 6.607351ms message: 'load-balancer-api-internal: resolved host name aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:15:40Z" - latency: 4.569497ms message: 'load-balancer-api-internal: tcp connection to aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:14:40Z" - latency: 6.995331ms message: 'load-balancer-api-internal: resolved host name aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:14:40Z" - latency: 5.300774ms message: 'load-balancer-api-internal: tcp connection to aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:13:40Z" - latency: 7.031289ms message: 'load-balancer-api-internal: resolved host name aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:13:40Z" - latency: 4.880455ms message: 'load-balancer-api-internal: tcp connection to aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:12:40Z" - latency: 6.716241ms message: 'load-balancer-api-internal: resolved host name aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:12:40Z" - latency: 4.414242ms message: 'load-balancer-api-internal: tcp connection to aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:11:40Z" - latency: 7.272936ms message: 'load-balancer-api-internal: resolved host name aa273cd6674174ba6a5002e3dc1a0305-431493f903f6b96e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:11:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:03:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-6-to-network-check-target-ip-10-0-134-48 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-6.ec2.internal uid: eb77757d-fc86-4b53-b970-49e39b76adda resourceVersion: "16496" uid: 3d11a801-d203-4794-87b5-414e54f0a31e spec: sourcePod: network-check-source-7d88cb55d8-c244p targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:10:40Z" message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.165801ms message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:17:40Z" - latency: 1.605844ms message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:16:40Z" - latency: 1.653208ms message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:15:40Z" - latency: 1.869855ms message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:14:40Z" - latency: 1.876929ms message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:13:40Z" - latency: 1.788146ms message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:12:40Z" - latency: 1.842144ms message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:11:40Z" - latency: 1.943748ms message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:10:40Z" - latency: 1.722632ms message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:09:40Z" - latency: 1.893868ms message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:08:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:03:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-6-to-network-check-target-ip-10-0-138-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-6.ec2.internal uid: eb77757d-fc86-4b53-b970-49e39b76adda resourceVersion: "16495" uid: 37e058f6-a271-4ebe-8a97-048eaa7ca38b spec: sourcePod: network-check-source-7d88cb55d8-c244p targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:10:40Z" message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 785.926µs message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:17:40Z" - latency: 1.094698ms message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:16:40Z" - latency: 798.908µs message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:15:40Z" - latency: 1.153665ms message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:14:40Z" - latency: 1.503837ms message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:13:40Z" - latency: 924.39µs message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:12:40Z" - latency: 1.648516ms message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:11:40Z" - latency: 852.039µs message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:10:40Z" - latency: 929.835µs message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:09:40Z" - latency: 865.889µs message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:08:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:03:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-6-to-network-check-target-ip-10-0-140-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-6.ec2.internal uid: eb77757d-fc86-4b53-b970-49e39b76adda resourceVersion: "16497" uid: 5e528548-f6af-4742-bf0c-1171ce221969 spec: sourcePod: network-check-source-7d88cb55d8-c244p targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:10:40Z" message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.126356ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:17:40Z" - latency: 2.025859ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:16:40Z" - latency: 2.180893ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:15:40Z" - latency: 2.21554ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:14:40Z" - latency: 2.168887ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:13:40Z" - latency: 2.20354ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:12:40Z" - latency: 2.20232ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:11:40Z" - latency: 2.380251ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:10:40Z" - latency: 2.19573ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:09:40Z" - latency: 2.301524ms message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:08:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:03:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-6-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-6.ec2.internal uid: eb77757d-fc86-4b53-b970-49e39b76adda resourceVersion: "15772" uid: 1518f09a-44c6-45b4-9f51-a2e68c13640f spec: sourcePod: network-check-source-7d88cb55d8-c244p targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T17:09:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.176137ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:15:40Z" - latency: 1.716911ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T17:15:40Z" - latency: 1.219862ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:14:40Z" - latency: 1.966733ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T17:14:40Z" - latency: 844.327µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:13:40Z" - latency: 2.145134ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T17:13:40Z" - latency: 851.711µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:12:40Z" - latency: 1.570269ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T17:12:40Z" - latency: 971.425µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:11:40Z" - latency: 2.104135ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T17:11:40Z" kind: List metadata: resourceVersion: ""