apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:52:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-204-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-204.ec2.internal uid: 5726eaf2-12be-471e-b726-1a4e4a5b8a91 resourceVersion: "65903" uid: a39d73f1-7d20-4da7-8f04-b3cc89841926 spec: sourcePod: network-check-source-7d88cb55d8-nzjkb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T13:59:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 917.195µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:34:57Z" - latency: 1.233205ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:33:57Z" - latency: 1.317846ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:32:57Z" - latency: 1.451692ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:31:57Z" - latency: 1.003474ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:30:57Z" - latency: 1.283286ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:29:57Z" - latency: 1.230062ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:28:57Z" - latency: 1.215109ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:27:57Z" - latency: 1.320461ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:26:57Z" - latency: 933.264µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:25:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:52:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-204-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-204.ec2.internal uid: 5726eaf2-12be-471e-b726-1a4e4a5b8a91 resourceVersion: "65905" uid: 78512aa4-fd82-40ab-8b95-de3ea65b8724 spec: sourcePod: network-check-source-7d88cb55d8-nzjkb targetEndpoint: affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T13:58:57Z" message: 'load-balancer-api-external: tcp connection to affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.449537ms message: 'load-balancer-api-external: tcp connection to affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:34:57Z" - latency: 6.764319ms message: 'load-balancer-api-external: resolved host name affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:34:57Z" - latency: 4.052136ms message: 'load-balancer-api-external: tcp connection to affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:33:57Z" - latency: 7.541187ms message: 'load-balancer-api-external: resolved host name affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:33:57Z" - latency: 6.488675ms message: 'load-balancer-api-external: tcp connection to affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:32:57Z" - latency: 7.715808ms message: 'load-balancer-api-external: resolved host name affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:32:57Z" - latency: 3.963469ms message: 'load-balancer-api-external: tcp connection to affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:31:57Z" - latency: 7.366838ms message: 'load-balancer-api-external: resolved host name affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:31:57Z" - latency: 4.117721ms message: 'load-balancer-api-external: tcp connection to affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:30:57Z" - latency: 6.776235ms message: 'load-balancer-api-external: resolved host name affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:30:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:52:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-204-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-204.ec2.internal uid: 5726eaf2-12be-471e-b726-1a4e4a5b8a91 resourceVersion: "65904" uid: b2ba3c79-0fee-4300-8c9b-8089638a91cd spec: sourcePod: network-check-source-7d88cb55d8-nzjkb targetEndpoint: affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T13:58:57Z" message: 'load-balancer-api-internal: tcp connection to affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.367804ms message: 'load-balancer-api-internal: tcp connection to affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:34:57Z" - latency: 6.663143ms message: 'load-balancer-api-internal: resolved host name affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:34:57Z" - latency: 6.070144ms message: 'load-balancer-api-internal: tcp connection to affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:33:57Z" - latency: 7.592984ms message: 'load-balancer-api-internal: resolved host name affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:33:57Z" - latency: 8.223905ms message: 'load-balancer-api-internal: tcp connection to affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:32:57Z" - latency: 7.645777ms message: 'load-balancer-api-internal: resolved host name affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:32:57Z" - latency: 6.102007ms message: 'load-balancer-api-internal: tcp connection to affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:31:57Z" - latency: 7.4378ms message: 'load-balancer-api-internal: resolved host name affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:31:57Z" - latency: 4.849928ms message: 'load-balancer-api-internal: tcp connection to affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:30:57Z" - latency: 6.841918ms message: 'load-balancer-api-internal: resolved host name affb4099dfa5a4e5388006beeefd3a94-151587c8014c0c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:30:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:52:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-204-to-network-check-target-ip-10-0-131-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-204.ec2.internal uid: 5726eaf2-12be-471e-b726-1a4e4a5b8a91 resourceVersion: "65901" uid: 818d2508-e560-4ce9-98bf-7eaec551e5ff spec: sourcePod: network-check-source-7d88cb55d8-nzjkb targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T13:59:57Z" message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.830118ms message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:34:57Z" - latency: 2.46389ms message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:33:57Z" - latency: 2.205291ms message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:32:57Z" - latency: 2.483187ms message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:31:57Z" - latency: 2.339122ms message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:30:57Z" - latency: 2.230412ms message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:29:57Z" - latency: 2.375473ms message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:28:57Z" - latency: 2.312779ms message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:27:57Z" - latency: 2.589262ms message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:26:57Z" - latency: 2.330746ms message: 'network-check-target-ip-10-0-131-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:25:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:52:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-204-to-network-check-target-ip-10-0-132-200 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-204.ec2.internal uid: 5726eaf2-12be-471e-b726-1a4e4a5b8a91 resourceVersion: "65900" uid: 18889941-03b7-4030-a5a8-6440de4bc6bf spec: sourcePod: network-check-source-7d88cb55d8-nzjkb targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T13:59:57Z" message: 'network-check-target-ip-10-0-132-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.212312ms message: 'network-check-target-ip-10-0-132-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:34:57Z" - latency: 2.230576ms message: 'network-check-target-ip-10-0-132-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:33:57Z" - latency: 2.291403ms message: 'network-check-target-ip-10-0-132-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:32:57Z" - latency: 2.611815ms message: 'network-check-target-ip-10-0-132-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:31:57Z" - latency: 2.148219ms message: 'network-check-target-ip-10-0-132-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:30:57Z" - latency: 2.171663ms message: 'network-check-target-ip-10-0-132-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:29:57Z" - latency: 2.239122ms message: 'network-check-target-ip-10-0-132-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:28:57Z" - latency: 2.209815ms message: 'network-check-target-ip-10-0-132-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:27:57Z" - latency: 2.433389ms message: 'network-check-target-ip-10-0-132-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:26:57Z" - latency: 2.25381ms message: 'network-check-target-ip-10-0-132-200: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:25:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:52:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-204-to-network-check-target-ip-10-0-143-204 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-204.ec2.internal uid: 5726eaf2-12be-471e-b726-1a4e4a5b8a91 resourceVersion: "65899" uid: 2b06d371-87df-4d80-a684-932da9734f29 spec: sourcePod: network-check-source-7d88cb55d8-nzjkb targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T13:59:57Z" message: 'network-check-target-ip-10-0-143-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 994.69µs message: 'network-check-target-ip-10-0-143-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:34:57Z" - latency: 1.009144ms message: 'network-check-target-ip-10-0-143-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:33:57Z" - latency: 1.245068ms message: 'network-check-target-ip-10-0-143-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:32:57Z" - latency: 1.17608ms message: 'network-check-target-ip-10-0-143-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:31:57Z" - latency: 1.126796ms message: 'network-check-target-ip-10-0-143-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:30:57Z" - latency: 887.016µs message: 'network-check-target-ip-10-0-143-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:29:57Z" - latency: 1.222386ms message: 'network-check-target-ip-10-0-143-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:28:57Z" - latency: 1.120863ms message: 'network-check-target-ip-10-0-143-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:27:57Z" - latency: 1.303372ms message: 'network-check-target-ip-10-0-143-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:26:57Z" - latency: 1.116037ms message: 'network-check-target-ip-10-0-143-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:25:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:52:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-204-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-204.ec2.internal uid: 5726eaf2-12be-471e-b726-1a4e4a5b8a91 resourceVersion: "65902" uid: e742a5f9-174a-4450-88cd-0dd34ab8c268 spec: sourcePod: network-check-source-7d88cb55d8-nzjkb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T13:58:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.027878ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:34:57Z" - latency: 2.130599ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T14:34:57Z" - latency: 1.015166ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:33:57Z" - latency: 1.796298ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T14:33:57Z" - latency: 1.182961ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:32:57Z" - latency: 1.892658ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T14:32:57Z" - latency: 983.845µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:31:57Z" - latency: 2.011729ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T14:31:57Z" - latency: 1.450146ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:30:57Z" - latency: 1.889033ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T14:30:57Z" kind: List metadata: resourceVersion: ""