apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T17:30:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-73-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-73.ec2.internal uid: 96a9b2f8-6aab-4118-a87e-0af7e25bce01 resourceVersion: "23251" uid: da2121b1-e87c-4a41-aa7c-ab9c28257275 spec: sourcePod: network-check-source-6f8b768455-kkgj6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-16T17:37:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 939.065µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:51:36Z" - latency: 782.982µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:50:36Z" - latency: 923.974µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:49:36Z" - latency: 729.624µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:48:36Z" - latency: 1.123548ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:47:36Z" - latency: 884.612µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:46:36Z" - latency: 933.274µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:45:36Z" - latency: 844.089µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:44:36Z" - latency: 902.182µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:43:36Z" - latency: 965.16µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:42:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T17:30:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-73-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-73.ec2.internal uid: 96a9b2f8-6aab-4118-a87e-0af7e25bce01 resourceVersion: "24763" uid: 92d985e6-5386-4195-95c6-6580d9915701 spec: sourcePod: network-check-source-6f8b768455-kkgj6 targetEndpoint: a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T17:36:36Z" message: 'load-balancer-api-external: tcp connection to a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.145972ms message: 'load-balancer-api-external: tcp connection to a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:54:36Z" - latency: 6.424313ms message: 'load-balancer-api-external: resolved host name a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T17:54:36Z" - latency: 3.908669ms message: 'load-balancer-api-external: tcp connection to a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:53:36Z" - latency: 8.562737ms message: 'load-balancer-api-external: resolved host name a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T17:53:36Z" - latency: 4.261207ms message: 'load-balancer-api-external: tcp connection to a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:52:36Z" - latency: 7.531227ms message: 'load-balancer-api-external: resolved host name a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T17:52:36Z" - latency: 4.163476ms message: 'load-balancer-api-external: tcp connection to a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:51:36Z" - latency: 8.492877ms message: 'load-balancer-api-external: resolved host name a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T17:51:36Z" - latency: 4.231449ms message: 'load-balancer-api-external: tcp connection to a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:50:36Z" - latency: 8.272245ms message: 'load-balancer-api-external: resolved host name a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T17:50:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T17:30:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-73-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-73.ec2.internal uid: 96a9b2f8-6aab-4118-a87e-0af7e25bce01 resourceVersion: "24762" uid: 023d7120-0b01-4010-9a40-0b9ba746620a spec: sourcePod: network-check-source-6f8b768455-kkgj6 targetEndpoint: a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T17:36:36Z" message: 'load-balancer-api-internal: tcp connection to a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.167241ms message: 'load-balancer-api-internal: tcp connection to a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:54:36Z" - latency: 6.398398ms message: 'load-balancer-api-internal: resolved host name a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T17:54:36Z" - latency: 7.127824ms message: 'load-balancer-api-internal: tcp connection to a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:53:36Z" - latency: 8.503002ms message: 'load-balancer-api-internal: resolved host name a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T17:53:36Z" - latency: 4.308843ms message: 'load-balancer-api-internal: tcp connection to a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:52:36Z" - latency: 7.506467ms message: 'load-balancer-api-internal: resolved host name a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T17:52:36Z" - latency: 4.200448ms message: 'load-balancer-api-internal: tcp connection to a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:51:36Z" - latency: 8.413907ms message: 'load-balancer-api-internal: resolved host name a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T17:51:36Z" - latency: 4.115074ms message: 'load-balancer-api-internal: tcp connection to a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:50:36Z" - latency: 8.283351ms message: 'load-balancer-api-internal: resolved host name a78759e2398dc4b4487a8f5904478ddc-0cf2a99c1dde41d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T17:50:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T17:30:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-73-to-network-check-target-ip-10-0-129-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-73.ec2.internal uid: 96a9b2f8-6aab-4118-a87e-0af7e25bce01 resourceVersion: "23249" uid: 86e3b2b2-9a80-4cd7-be71-0e80803bdd4f spec: sourcePod: network-check-source-6f8b768455-kkgj6 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-16T17:37:36Z" message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.734892ms message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:51:36Z" - latency: 1.674671ms message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:50:36Z" - latency: 1.924462ms message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:49:36Z" - latency: 1.949518ms message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:48:36Z" - latency: 1.925613ms message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:47:36Z" - latency: 1.745273ms message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:46:36Z" - latency: 1.958277ms message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:45:36Z" - latency: 1.671354ms message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:44:36Z" - latency: 2.124127ms message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:43:36Z" - latency: 2.030054ms message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:42:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T17:30:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-73-to-network-check-target-ip-10-0-134-96 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-73.ec2.internal uid: 96a9b2f8-6aab-4118-a87e-0af7e25bce01 resourceVersion: "23250" uid: 6f2ab15c-b73e-4d7a-a9e7-bd1aab0021d1 spec: sourcePod: network-check-source-6f8b768455-kkgj6 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-16T17:37:36Z" message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.774272ms message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:51:36Z" - latency: 2.263215ms message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:50:36Z" - latency: 6.170251ms message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:49:36Z" - latency: 2.209801ms message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:48:36Z" - latency: 2.267278ms message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:47:36Z" - latency: 2.254608ms message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:46:36Z" - latency: 2.123962ms message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:45:36Z" - latency: 2.197802ms message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:44:36Z" - latency: 2.160607ms message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:43:36Z" - latency: 2.11336ms message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:42:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T17:30:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-73-to-network-check-target-ip-10-0-138-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-73.ec2.internal uid: 96a9b2f8-6aab-4118-a87e-0af7e25bce01 resourceVersion: "23248" uid: e8b116b3-df1e-452e-bb84-c881cdba86d0 spec: sourcePod: network-check-source-6f8b768455-kkgj6 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-16T17:37:36Z" message: 'network-check-target-ip-10-0-138-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 811.234µs message: 'network-check-target-ip-10-0-138-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:51:36Z" - latency: 729.221µs message: 'network-check-target-ip-10-0-138-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:50:36Z" - latency: 1.242302ms message: 'network-check-target-ip-10-0-138-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:49:36Z" - latency: 745.053µs message: 'network-check-target-ip-10-0-138-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:48:36Z" - latency: 945.34µs message: 'network-check-target-ip-10-0-138-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:47:36Z" - latency: 895.076µs message: 'network-check-target-ip-10-0-138-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:46:36Z" - latency: 853.635µs message: 'network-check-target-ip-10-0-138-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:45:36Z" - latency: 724.771µs message: 'network-check-target-ip-10-0-138-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:44:36Z" - latency: 815.142µs message: 'network-check-target-ip-10-0-138-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:43:36Z" - latency: 1.23765ms message: 'network-check-target-ip-10-0-138-73: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:42:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T17:30:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-73-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-73.ec2.internal uid: 96a9b2f8-6aab-4118-a87e-0af7e25bce01 resourceVersion: "24761" uid: fec0210e-3977-4c56-a89f-e6ca5ebfafb5 spec: sourcePod: network-check-source-6f8b768455-kkgj6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-16T17:36:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.280734ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:54:36Z" - latency: 1.572707ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T17:54:36Z" - latency: 947.533µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:53:36Z" - latency: 1.950535ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T17:53:36Z" - latency: 857.747µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:52:36Z" - latency: 1.961672ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T17:52:36Z" - latency: 912.394µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:51:36Z" - latency: 1.823974ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T17:51:36Z" - latency: 836.172µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T17:50:36Z" - latency: 1.560405ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T17:50:36Z" kind: List metadata: resourceVersion: ""