apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T17:15:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-64-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-64.ec2.internal uid: 375dcbf2-9d08-4320-817d-6949e1624d86 resourceVersion: "43878" uid: 12990fd6-d5c7-4e38-b30d-12e72308c06e spec: sourcePod: network-check-source-6947749cfc-ff84f targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-12T17:22:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.010853ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:43:42Z" - latency: 1.070241ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:42:42Z" - latency: 886.932µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:41:42Z" - latency: 1.002169ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:40:42Z" - latency: 1.143572ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:39:42Z" - latency: 984.351µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:38:42Z" - latency: 772.515µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:37:42Z" - latency: 1.200367ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:36:42Z" - latency: 1.172336ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:35:42Z" - latency: 1.077787ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:34:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T17:15:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-64-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-64.ec2.internal uid: 375dcbf2-9d08-4320-817d-6949e1624d86 resourceVersion: "45972" uid: 32e9791a-5d36-4647-86f4-5be08995f136 spec: sourcePod: network-check-source-6947749cfc-ff84f targetEndpoint: a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T17:21:42Z" message: 'load-balancer-api-external: tcp connection to a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.849927ms message: 'load-balancer-api-external: tcp connection to a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:45:42Z" - latency: 8.863398ms message: 'load-balancer-api-external: resolved host name a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:45:42Z" - latency: 5.499948ms message: 'load-balancer-api-external: tcp connection to a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:44:42Z" - latency: 8.492595ms message: 'load-balancer-api-external: resolved host name a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:44:42Z" - latency: 5.225161ms message: 'load-balancer-api-external: tcp connection to a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:43:42Z" - latency: 8.251363ms message: 'load-balancer-api-external: resolved host name a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:43:42Z" - latency: 4.288308ms message: 'load-balancer-api-external: tcp connection to a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:42:42Z" - latency: 8.871523ms message: 'load-balancer-api-external: resolved host name a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:42:42Z" - latency: 5.561874ms message: 'load-balancer-api-external: tcp connection to a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:41:42Z" - latency: 8.155279ms message: 'load-balancer-api-external: resolved host name a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:41:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T17:15:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-64-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-64.ec2.internal uid: 375dcbf2-9d08-4320-817d-6949e1624d86 resourceVersion: "45973" uid: 93a802de-5eff-45b9-bd93-b66c17f2b9bb spec: sourcePod: network-check-source-6947749cfc-ff84f targetEndpoint: a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T17:21:42Z" message: 'load-balancer-api-internal: tcp connection to a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.882064ms message: 'load-balancer-api-internal: tcp connection to a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:45:42Z" - latency: 8.790647ms message: 'load-balancer-api-internal: resolved host name a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:45:42Z" - latency: 5.781503ms message: 'load-balancer-api-internal: tcp connection to a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:44:42Z" - latency: 8.556234ms message: 'load-balancer-api-internal: resolved host name a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:44:42Z" - latency: 5.059189ms message: 'load-balancer-api-internal: tcp connection to a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:43:42Z" - latency: 8.232199ms message: 'load-balancer-api-internal: resolved host name a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:43:42Z" - latency: 4.19258ms message: 'load-balancer-api-internal: tcp connection to a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:42:42Z" - latency: 8.834997ms message: 'load-balancer-api-internal: resolved host name a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:42:42Z" - latency: 3.555853ms message: 'load-balancer-api-internal: tcp connection to a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:41:42Z" - latency: 8.120629ms message: 'load-balancer-api-internal: resolved host name a1fe85472b35247d791f54662704a6ad-23623ff1f0efe286.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:41:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T17:15:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-64-to-network-check-target-ip-10-0-128-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-64.ec2.internal uid: 375dcbf2-9d08-4320-817d-6949e1624d86 resourceVersion: "43876" uid: b9f3812a-a4c1-4503-ab3c-bd3daf53e6ad spec: sourcePod: network-check-source-6947749cfc-ff84f targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-12T17:22:42Z" message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.075656ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:43:42Z" - latency: 2.107816ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:42:42Z" - latency: 2.05176ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:41:42Z" - latency: 1.82151ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:40:42Z" - latency: 2.259278ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:39:42Z" - latency: 2.15622ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:38:42Z" - latency: 2.149605ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:37:42Z" - latency: 2.291553ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:36:42Z" - latency: 2.126861ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:35:42Z" - latency: 2.021683ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:34:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T17:15:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-64-to-network-check-target-ip-10-0-130-182 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-64.ec2.internal uid: 375dcbf2-9d08-4320-817d-6949e1624d86 resourceVersion: "43877" uid: 92b99bad-102e-46ad-a8cc-5397a7687b78 spec: sourcePod: network-check-source-6947749cfc-ff84f targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-12T17:22:42Z" message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.970126ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:43:42Z" - latency: 2.027146ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:42:42Z" - latency: 2.13121ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:41:42Z" - latency: 2.049626ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:40:42Z" - latency: 2.292108ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:39:42Z" - latency: 1.970677ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:38:42Z" - latency: 2.121921ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:37:42Z" - latency: 2.225993ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:36:42Z" - latency: 2.125676ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:35:42Z" - latency: 2.302161ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:34:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T17:15:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-64-to-network-check-target-ip-10-0-134-64 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-64.ec2.internal uid: 375dcbf2-9d08-4320-817d-6949e1624d86 resourceVersion: "43875" uid: 1f1db4b2-a21c-4e6c-83e3-eec00e35c7fa spec: sourcePod: network-check-source-6947749cfc-ff84f targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-12T17:22:42Z" message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 790.232µs message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:43:42Z" - latency: 797.824µs message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:42:42Z" - latency: 1.266339ms message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:41:42Z" - latency: 1.203413ms message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:40:42Z" - latency: 1.001312ms message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:39:42Z" - latency: 1.016403ms message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:38:42Z" - latency: 834.924µs message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:37:42Z" - latency: 1.415991ms message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:36:42Z" - latency: 1.193484ms message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:35:42Z" - latency: 1.54254ms message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:34:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T17:15:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-64-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-64.ec2.internal uid: 375dcbf2-9d08-4320-817d-6949e1624d86 resourceVersion: "45971" uid: 5ac5e2f9-aa43-4005-be4c-c986d4bbce39 spec: sourcePod: network-check-source-6947749cfc-ff84f targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-12T17:21:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.153492ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:45:42Z" - latency: 1.607783ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T17:45:42Z" - latency: 888.157µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:44:42Z" - latency: 1.846638ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T17:44:42Z" - latency: 1.155158ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:43:42Z" - latency: 1.92269ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T17:43:42Z" - latency: 802.495µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:42:42Z" - latency: 2.389165ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T17:42:42Z" - latency: 1.088916ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:41:42Z" - latency: 1.689567ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T17:41:42Z" kind: List metadata: resourceVersion: ""