apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T06:44:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-199-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-199.ec2.internal uid: d3f75f39-c4ae-4e42-9596-6d1278cd83c6 resourceVersion: "23914" uid: 986430a1-de66-4a1c-92e5-4ab5c05ce48e spec: sourcePod: network-check-source-6f8b768455-dfj4j targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-15T06:51:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.022593ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:12:30Z" - latency: 1.00265ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:11:30Z" - latency: 1.218034ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:10:30Z" - latency: 1.020212ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:09:30Z" - latency: 1.127272ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:08:30Z" - latency: 1.344115ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:07:30Z" - latency: 1.185285ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:06:30Z" - latency: 1.020603ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:05:30Z" - latency: 1.042629ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:04:30Z" - latency: 875.253µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:03:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T06:44:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-199-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-199.ec2.internal uid: d3f75f39-c4ae-4e42-9596-6d1278cd83c6 resourceVersion: "22336" uid: 786e601f-5310-4ac8-a774-e600d4f6fa8a spec: sourcePod: network-check-source-6f8b768455-dfj4j targetEndpoint: a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-15T06:50:30Z" message: 'load-balancer-api-external: tcp connection to a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.752612ms message: 'load-balancer-api-external: tcp connection to a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:08:30Z" - latency: 7.95731ms message: 'load-balancer-api-external: resolved host name a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:08:30Z" - latency: 3.868638ms message: 'load-balancer-api-external: tcp connection to a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:07:30Z" - latency: 11.032154ms message: 'load-balancer-api-external: resolved host name a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:07:30Z" - latency: 4.927379ms message: 'load-balancer-api-external: tcp connection to a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:06:30Z" - latency: 7.813604ms message: 'load-balancer-api-external: resolved host name a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:06:30Z" - latency: 5.883195ms message: 'load-balancer-api-external: tcp connection to a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:05:30Z" - latency: 10.675837ms message: 'load-balancer-api-external: resolved host name a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:05:30Z" - latency: 4.146602ms message: 'load-balancer-api-external: tcp connection to a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:04:30Z" - latency: 9.068142ms message: 'load-balancer-api-external: resolved host name a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:04:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T06:44:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-199-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-199.ec2.internal uid: d3f75f39-c4ae-4e42-9596-6d1278cd83c6 resourceVersion: "22337" uid: ff2f81e7-3ae5-4c39-9815-d7be9a1d0263 spec: sourcePod: network-check-source-6f8b768455-dfj4j targetEndpoint: a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-15T06:50:30Z" message: 'load-balancer-api-internal: tcp connection to a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.771593ms message: 'load-balancer-api-internal: tcp connection to a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:08:30Z" - latency: 8.138742ms message: 'load-balancer-api-internal: resolved host name a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:08:30Z" - latency: 4.39191ms message: 'load-balancer-api-internal: tcp connection to a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:07:30Z" - latency: 11.084756ms message: 'load-balancer-api-internal: resolved host name a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:07:30Z" - latency: 4.923018ms message: 'load-balancer-api-internal: tcp connection to a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:06:30Z" - latency: 7.791813ms message: 'load-balancer-api-internal: resolved host name a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:06:30Z" - latency: 5.872399ms message: 'load-balancer-api-internal: tcp connection to a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:05:30Z" - latency: 10.730201ms message: 'load-balancer-api-internal: resolved host name a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:05:30Z" - latency: 4.11677ms message: 'load-balancer-api-internal: tcp connection to a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:04:30Z" - latency: 9.182853ms message: 'load-balancer-api-internal: resolved host name a5a07621a7cc941059f37cb2b5ce8555-cfe7dc51b09dcb6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:04:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T06:44:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-199-to-network-check-target-ip-10-0-128-50 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-199.ec2.internal uid: d3f75f39-c4ae-4e42-9596-6d1278cd83c6 resourceVersion: "23913" uid: 7b14ef55-8933-4915-933c-6afa99a213b6 spec: sourcePod: network-check-source-6f8b768455-dfj4j targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-15T06:51:30Z" message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.419544ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:12:30Z" - latency: 2.491469ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:11:30Z" - latency: 2.569276ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:10:30Z" - latency: 2.396702ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:09:30Z" - latency: 2.39663ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:08:30Z" - latency: 2.253134ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:07:30Z" - latency: 2.272495ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:06:30Z" - latency: 2.609773ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:05:30Z" - latency: 2.50764ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:04:30Z" - latency: 2.412287ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:03:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T06:44:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-199-to-network-check-target-ip-10-0-133-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-199.ec2.internal uid: d3f75f39-c4ae-4e42-9596-6d1278cd83c6 resourceVersion: "23912" uid: a2db1883-537d-4951-9847-1c2c9bdcda95 spec: sourcePod: network-check-source-6f8b768455-dfj4j targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-15T06:51:30Z" message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.383063ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:12:30Z" - latency: 2.117327ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:11:30Z" - latency: 2.387006ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:10:30Z" - latency: 2.236679ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:09:30Z" - latency: 3.048512ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:08:30Z" - latency: 2.271915ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:07:30Z" - latency: 2.263416ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:06:30Z" - latency: 2.343426ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:05:30Z" - latency: 2.507956ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:04:30Z" - latency: 2.311631ms message: 'network-check-target-ip-10-0-133-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:03:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T06:44:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-199-to-network-check-target-ip-10-0-137-199 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-199.ec2.internal uid: d3f75f39-c4ae-4e42-9596-6d1278cd83c6 resourceVersion: "23911" uid: ac1a469b-85c2-441b-bee5-6c77d686d0fa spec: sourcePod: network-check-source-6f8b768455-dfj4j targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-15T06:51:30Z" message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 843.323µs message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:12:30Z" - latency: 854.431µs message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:11:30Z" - latency: 931µs message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:10:30Z" - latency: 1.506877ms message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:09:30Z" - latency: 1.521364ms message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:08:30Z" - latency: 930.2µs message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:07:30Z" - latency: 945.713µs message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:06:30Z" - latency: 1.02046ms message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:05:30Z" - latency: 1.450867ms message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:04:30Z" - latency: 851.741µs message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:03:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T06:44:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-199-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-199.ec2.internal uid: d3f75f39-c4ae-4e42-9596-6d1278cd83c6 resourceVersion: "22335" uid: 800f4424-2da5-43c2-94ab-a903a39bee01 spec: sourcePod: network-check-source-6f8b768455-dfj4j targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-15T06:50:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.009372ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:08:30Z" - latency: 1.997282ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T07:08:30Z" - latency: 1.226662ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:07:30Z" - latency: 1.954948ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T07:07:30Z" - latency: 938.663µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:06:30Z" - latency: 1.794688ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T07:06:30Z" - latency: 1.068133ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:05:30Z" - latency: 2.753573ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T07:05:30Z" - latency: 1.295673ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:04:30Z" - latency: 2.307817ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T07:04:30Z" kind: List metadata: resourceVersion: ""