apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T17:19:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-98-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-98.ec2.internal uid: b88546e2-3a22-42b5-9337-5e51c77fb746 resourceVersion: "19234" uid: b2990a1f-c95d-4c3e-9be5-89244a421ee7 spec: sourcePod: network-check-source-7bc5b6bf85-29fxt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T17:26:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.077103ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:40:55Z" - latency: 964.656µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:39:55Z" - latency: 959.344µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:38:55Z" - latency: 944.756µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:37:55Z" - latency: 1.23263ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:36:55Z" - latency: 833.717µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:35:55Z" - latency: 920.28µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:34:55Z" - latency: 1.004303ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:33:55Z" - latency: 1.015027ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:32:55Z" - latency: 880.057µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:31:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T17:19:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-98-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-98.ec2.internal uid: b88546e2-3a22-42b5-9337-5e51c77fb746 resourceVersion: "20555" uid: fffec4e9-cbc2-4dbb-972f-1a371a90dc49 spec: sourcePod: network-check-source-7bc5b6bf85-29fxt targetEndpoint: a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T17:25:55Z" message: 'load-balancer-api-external: tcp connection to a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.413584ms message: 'load-balancer-api-external: tcp connection to a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:43:55Z" - latency: 9.399502ms message: 'load-balancer-api-external: resolved host name a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:43:55Z" - latency: 4.081277ms message: 'load-balancer-api-external: tcp connection to a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:42:55Z" - latency: 9.615833ms message: 'load-balancer-api-external: resolved host name a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:42:55Z" - latency: 4.748092ms message: 'load-balancer-api-external: tcp connection to a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:41:55Z" - latency: 8.571564ms message: 'load-balancer-api-external: resolved host name a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:41:55Z" - latency: 5.147601ms message: 'load-balancer-api-external: tcp connection to a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:40:55Z" - latency: 7.279381ms message: 'load-balancer-api-external: resolved host name a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:40:55Z" - latency: 4.986205ms message: 'load-balancer-api-external: tcp connection to a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:39:55Z" - latency: 8.481559ms message: 'load-balancer-api-external: resolved host name a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:39:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T17:19:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-98-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-98.ec2.internal uid: b88546e2-3a22-42b5-9337-5e51c77fb746 resourceVersion: "20554" uid: 72079dcc-cbb2-48ec-a5e7-100f8fae0c0c spec: sourcePod: network-check-source-7bc5b6bf85-29fxt targetEndpoint: a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T17:25:55Z" message: 'load-balancer-api-internal: tcp connection to a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.436809ms message: 'load-balancer-api-internal: tcp connection to a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:43:55Z" - latency: 9.660408ms message: 'load-balancer-api-internal: resolved host name a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:43:55Z" - latency: 4.898667ms message: 'load-balancer-api-internal: tcp connection to a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:42:55Z" - latency: 9.531581ms message: 'load-balancer-api-internal: resolved host name a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:42:55Z" - latency: 4.659628ms message: 'load-balancer-api-internal: tcp connection to a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:41:55Z" - latency: 8.647875ms message: 'load-balancer-api-internal: resolved host name a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:41:55Z" - latency: 4.971575ms message: 'load-balancer-api-internal: tcp connection to a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:40:55Z" - latency: 7.254326ms message: 'load-balancer-api-internal: resolved host name a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:40:55Z" - latency: 5.283903ms message: 'load-balancer-api-internal: tcp connection to a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:39:55Z" - latency: 8.554476ms message: 'load-balancer-api-internal: resolved host name a9545f850de944c66953c3ccdea2beed-ddf27217050db176.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:39:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T17:19:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-98-to-network-check-target-ip-10-0-130-98 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-98.ec2.internal uid: b88546e2-3a22-42b5-9337-5e51c77fb746 resourceVersion: "19231" uid: e2068a97-9505-4f1c-a563-b768dc31e57e spec: sourcePod: network-check-source-7bc5b6bf85-29fxt targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T17:26:55Z" message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 775.641µs message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:40:55Z" - latency: 927.924µs message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:39:55Z" - latency: 903.032µs message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:38:55Z" - latency: 744.672µs message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:37:55Z" - latency: 819.204µs message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:36:55Z" - latency: 1.026137ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:35:55Z" - latency: 876.563µs message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:34:55Z" - latency: 1.004156ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:33:55Z" - latency: 890.316µs message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:32:55Z" - latency: 1.181759ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:31:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T17:19:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-98-to-network-check-target-ip-10-0-134-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-98.ec2.internal uid: b88546e2-3a22-42b5-9337-5e51c77fb746 resourceVersion: "19232" uid: 7a32b6c0-c26f-4aa6-ab57-251b10fd7469 spec: sourcePod: network-check-source-7bc5b6bf85-29fxt targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T17:26:55Z" message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.296846ms message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:40:55Z" - latency: 2.287442ms message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:39:55Z" - latency: 2.598249ms message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:38:55Z" - latency: 2.372995ms message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:37:55Z" - latency: 2.313556ms message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:36:55Z" - latency: 2.525262ms message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:35:55Z" - latency: 2.32888ms message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:34:55Z" - latency: 2.365128ms message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:33:55Z" - latency: 2.506616ms message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:32:55Z" - latency: 2.409895ms message: 'network-check-target-ip-10-0-134-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:31:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T17:19:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-98-to-network-check-target-ip-10-0-139-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-98.ec2.internal uid: b88546e2-3a22-42b5-9337-5e51c77fb746 resourceVersion: "19233" uid: 3b3a564b-9606-4715-83c9-d75e11a72b9c spec: sourcePod: network-check-source-7bc5b6bf85-29fxt targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T17:26:55Z" message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.131772ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:40:55Z" - latency: 2.181276ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:39:55Z" - latency: 2.140634ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:38:55Z" - latency: 2.234754ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:37:55Z" - latency: 2.223582ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:36:55Z" - latency: 2.337512ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:35:55Z" - latency: 2.170267ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:34:55Z" - latency: 2.255252ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:33:55Z" - latency: 2.278918ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:32:55Z" - latency: 2.336072ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:31:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T17:19:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-98-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-98.ec2.internal uid: b88546e2-3a22-42b5-9337-5e51c77fb746 resourceVersion: "20553" uid: 13d649ee-ba81-4db7-bfde-92d6aa1001bf spec: sourcePod: network-check-source-7bc5b6bf85-29fxt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T17:25:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.101321ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:43:55Z" - latency: 1.870116ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T17:43:55Z" - latency: 763.276µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:42:55Z" - latency: 1.132563ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T17:42:55Z" - latency: 743.795µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:41:55Z" - latency: 1.540339ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T17:41:55Z" - latency: 799.25µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:40:55Z" - latency: 1.489973ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T17:40:55Z" - latency: 919.891µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:39:55Z" - latency: 1.605715ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T17:39:55Z" kind: List metadata: resourceVersion: ""