apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T14:51:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-117-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-117.ec2.internal uid: 1c839af1-b15c-4a37-9fe7-166d60b46a24 resourceVersion: "82100" uid: e263b5a7-e255-427b-82c6-6a0f88ff27e4 spec: sourcePod: network-check-source-7d88cb55d8-9shzj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-30T14:58:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.007639ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:54:36Z" - latency: 1.058561ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:53:36Z" - latency: 3.020023ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:52:36Z" - latency: 989.577µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:51:36Z" - latency: 1.397476ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:50:36Z" - latency: 1.607012ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:49:36Z" - latency: 1.531417ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:48:36Z" - latency: 1.40208ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:47:36Z" - latency: 1.35206ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:46:36Z" - latency: 1.071147ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:45:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T14:51:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-117-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-117.ec2.internal uid: 1c839af1-b15c-4a37-9fe7-166d60b46a24 resourceVersion: "78939" uid: bfd2d3bb-e3cb-43fc-8253-b66a53d682ef spec: sourcePod: network-check-source-7d88cb55d8-9shzj targetEndpoint: ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T14:57:36Z" message: 'load-balancer-api-external: tcp connection to ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.378801ms message: 'load-balancer-api-external: tcp connection to ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:51:36Z" - latency: 7.261683ms message: 'load-balancer-api-external: resolved host name ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T15:51:36Z" - latency: 4.211895ms message: 'load-balancer-api-external: tcp connection to ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:50:36Z" - latency: 6.426893ms message: 'load-balancer-api-external: resolved host name ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T15:50:36Z" - latency: 4.651395ms message: 'load-balancer-api-external: tcp connection to ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:49:36Z" - latency: 7.139778ms message: 'load-balancer-api-external: resolved host name ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T15:49:36Z" - latency: 6.72037ms message: 'load-balancer-api-external: tcp connection to ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:48:36Z" - latency: 6.487923ms message: 'load-balancer-api-external: resolved host name ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T15:48:36Z" - latency: 5.179019ms message: 'load-balancer-api-external: tcp connection to ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:47:36Z" - latency: 7.785313ms message: 'load-balancer-api-external: resolved host name ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T15:47:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T14:51:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-117-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-117.ec2.internal uid: 1c839af1-b15c-4a37-9fe7-166d60b46a24 resourceVersion: "78938" uid: ea25f580-e71a-49d8-9991-a2175abf6288 spec: sourcePod: network-check-source-7d88cb55d8-9shzj targetEndpoint: ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T14:57:36Z" message: 'load-balancer-api-internal: tcp connection to ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.368637ms message: 'load-balancer-api-internal: tcp connection to ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:51:36Z" - latency: 7.321146ms message: 'load-balancer-api-internal: resolved host name ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T15:51:36Z" - latency: 4.340126ms message: 'load-balancer-api-internal: tcp connection to ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:50:36Z" - latency: 6.36149ms message: 'load-balancer-api-internal: resolved host name ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T15:50:36Z" - latency: 3.415996ms message: 'load-balancer-api-internal: tcp connection to ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:49:36Z" - latency: 7.01576ms message: 'load-balancer-api-internal: resolved host name ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T15:49:36Z" - latency: 5.415131ms message: 'load-balancer-api-internal: tcp connection to ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:48:36Z" - latency: 6.578126ms message: 'load-balancer-api-internal: resolved host name ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T15:48:36Z" - latency: 6.030322ms message: 'load-balancer-api-internal: tcp connection to ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:47:36Z" - latency: 7.710766ms message: 'load-balancer-api-internal: resolved host name ad02f5989afe249c193ee4ea1cbb3bcd-334801bf56cd1028.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T15:47:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T14:51:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-117-to-network-check-target-ip-10-0-130-38 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-117.ec2.internal uid: 1c839af1-b15c-4a37-9fe7-166d60b46a24 resourceVersion: "82099" uid: 215f1526-d715-4af5-baae-17bf6adeb8ac spec: sourcePod: network-check-source-7d88cb55d8-9shzj targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-30T14:58:36Z" message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.841685ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:54:36Z" - latency: 2.688276ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:53:36Z" - latency: 4.523034ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:52:36Z" - latency: 2.944075ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:51:36Z" - latency: 2.605191ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:50:36Z" - latency: 2.576218ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:49:36Z" - latency: 2.561888ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:48:36Z" - latency: 2.169828ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:47:36Z" - latency: 2.836733ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:46:36Z" - latency: 2.314228ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:45:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T14:51:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-117-to-network-check-target-ip-10-0-133-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-117.ec2.internal uid: 1c839af1-b15c-4a37-9fe7-166d60b46a24 resourceVersion: "82097" uid: 53d85e4d-6f9f-4ab1-8c3b-b9e733dca324 spec: sourcePod: network-check-source-7d88cb55d8-9shzj targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-30T14:58:36Z" message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.1968ms message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:54:36Z" - latency: 1.282159ms message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:53:36Z" - latency: 1.098722ms message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:52:36Z" - latency: 1.102156ms message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:51:36Z" - latency: 1.058258ms message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:50:36Z" - latency: 1.026125ms message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:49:36Z" - latency: 1.007133ms message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:48:36Z" - latency: 1.537476ms message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:47:36Z" - latency: 1.084725ms message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:46:36Z" - latency: 1.319932ms message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:45:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T14:51:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-117-to-network-check-target-ip-10-0-133-92 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-117.ec2.internal uid: 1c839af1-b15c-4a37-9fe7-166d60b46a24 resourceVersion: "82098" uid: d816ff3c-dc6c-483e-9df5-61ab169b5a03 spec: sourcePod: network-check-source-7d88cb55d8-9shzj targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-30T14:58:36Z" message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.470553ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:54:36Z" - latency: 2.348585ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:53:36Z" - latency: 3.399448ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:52:36Z" - latency: 2.502651ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:51:36Z" - latency: 2.329431ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:50:36Z" - latency: 2.414677ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:49:36Z" - latency: 2.325276ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:48:36Z" - latency: 2.545703ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:47:36Z" - latency: 2.334887ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:46:36Z" - latency: 2.029137ms message: 'network-check-target-ip-10-0-133-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:45:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T14:51:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-117-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-117.ec2.internal uid: 1c839af1-b15c-4a37-9fe7-166d60b46a24 resourceVersion: "78935" uid: 5e617ae9-60e2-402d-9f44-230f28efeb88 spec: sourcePod: network-check-source-7d88cb55d8-9shzj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-30T14:57:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.175611ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:51:36Z" - latency: 2.14834ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T15:51:36Z" - latency: 1.210222ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:50:36Z" - latency: 1.925525ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T15:50:36Z" - latency: 954.397µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:49:36Z" - latency: 1.8425ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T15:49:36Z" - latency: 979.372µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:48:36Z" - latency: 1.884548ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T15:48:36Z" - latency: 1.366897ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T15:47:36Z" - latency: 1.949256ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T15:47:36Z" kind: List metadata: resourceVersion: ""