apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:38:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-199-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-199.ec2.internal uid: 4952478e-9274-454c-ba18-190a2d4e0453 resourceVersion: "71009" uid: faa2616b-3192-43d4-ad4d-369ad8bb6026 spec: sourcePod: network-check-source-7d88cb55d8-5x9s7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T13:45:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.384515ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:20:16Z" - latency: 982.203µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:19:16Z" - latency: 1.209494ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:18:16Z" - latency: 1.100514ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:17:16Z" - latency: 1.446979ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:16:16Z" - latency: 1.096703ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:15:16Z" - latency: 910.418µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:14:16Z" - latency: 1.036616ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:13:16Z" - latency: 1.196147ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:12:16Z" - latency: 923.147µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:11:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:38:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-199-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-199.ec2.internal uid: 4952478e-9274-454c-ba18-190a2d4e0453 resourceVersion: "71012" uid: 525fd9b8-d02f-4058-bc56-5f7889ac1219 spec: sourcePod: network-check-source-7d88cb55d8-5x9s7 targetEndpoint: a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T13:44:16Z" message: 'load-balancer-api-external: tcp connection to a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.951695ms message: 'load-balancer-api-external: tcp connection to a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:20:16Z" - latency: 10.087375ms message: 'load-balancer-api-external: resolved host name a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:20:16Z" - latency: 4.691562ms message: 'load-balancer-api-external: tcp connection to a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:19:16Z" - latency: 8.821628ms message: 'load-balancer-api-external: resolved host name a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:19:16Z" - latency: 3.952776ms message: 'load-balancer-api-external: tcp connection to a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:18:16Z" - latency: 8.494911ms message: 'load-balancer-api-external: resolved host name a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:18:16Z" - latency: 3.902431ms message: 'load-balancer-api-external: tcp connection to a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:17:16Z" - latency: 8.48646ms message: 'load-balancer-api-external: resolved host name a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:17:16Z" - latency: 2.907021ms message: 'load-balancer-api-external: tcp connection to a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:16:16Z" - latency: 8.663648ms message: 'load-balancer-api-external: resolved host name a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:16:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:38:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-199-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-199.ec2.internal uid: 4952478e-9274-454c-ba18-190a2d4e0453 resourceVersion: "71011" uid: 3cc6959f-d80c-46e2-a361-3911c4c66580 spec: sourcePod: network-check-source-7d88cb55d8-5x9s7 targetEndpoint: a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T13:44:16Z" message: 'load-balancer-api-internal: tcp connection to a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.985772ms message: 'load-balancer-api-internal: tcp connection to a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:20:16Z" - latency: 10.004766ms message: 'load-balancer-api-internal: resolved host name a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:20:16Z" - latency: 4.72825ms message: 'load-balancer-api-internal: tcp connection to a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:19:16Z" - latency: 8.748805ms message: 'load-balancer-api-internal: resolved host name a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:19:16Z" - latency: 3.940928ms message: 'load-balancer-api-internal: tcp connection to a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:18:16Z" - latency: 8.520917ms message: 'load-balancer-api-internal: resolved host name a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:18:16Z" - latency: 3.90604ms message: 'load-balancer-api-internal: tcp connection to a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:17:16Z" - latency: 8.521391ms message: 'load-balancer-api-internal: resolved host name a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:17:16Z" - latency: 13.082074ms message: 'load-balancer-api-internal: tcp connection to a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:16:16Z" - latency: 8.765529ms message: 'load-balancer-api-internal: resolved host name a0127f4cd09464b9eb60cb7a54016ff7-5af16f43cfd343b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:16:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:38:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-199-to-network-check-target-ip-10-0-129-199 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-199.ec2.internal uid: 4952478e-9274-454c-ba18-190a2d4e0453 resourceVersion: "71005" uid: 6a5e8beb-b755-4389-9e79-ab05f6958992 spec: sourcePod: network-check-source-7d88cb55d8-5x9s7 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T13:45:16Z" message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.022812ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:20:16Z" - latency: 884.752µs message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:19:16Z" - latency: 978.304µs message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:18:16Z" - latency: 828.457µs message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:17:16Z" - latency: 855.445µs message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:16:16Z" - latency: 1.096001ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:15:16Z" - latency: 1.009476ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:14:16Z" - latency: 1.02583ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:13:16Z" - latency: 933.096µs message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:12:16Z" - latency: 1.215274ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:11:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:38:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-199-to-network-check-target-ip-10-0-136-88 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-199.ec2.internal uid: 4952478e-9274-454c-ba18-190a2d4e0453 resourceVersion: "71006" uid: 4d501392-a7f9-408b-9b3b-ed287cb733d4 spec: sourcePod: network-check-source-7d88cb55d8-5x9s7 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T13:45:16Z" message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.62052ms message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:20:16Z" - latency: 2.508699ms message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:19:16Z" - latency: 1.928329ms message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:18:16Z" - latency: 2.396611ms message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:17:16Z" - latency: 2.162745ms message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:16:16Z" - latency: 2.648363ms message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:15:16Z" - latency: 2.134172ms message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:14:16Z" - latency: 2.353117ms message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:13:16Z" - latency: 1.931349ms message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:12:16Z" - latency: 2.435461ms message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:11:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:38:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-199-to-network-check-target-ip-10-0-137-60 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-199.ec2.internal uid: 4952478e-9274-454c-ba18-190a2d4e0453 resourceVersion: "71008" uid: 81f5cefc-73c2-4e20-916b-1c5b700d9031 spec: sourcePod: network-check-source-7d88cb55d8-5x9s7 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T13:45:16Z" message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.479439ms message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:20:16Z" - latency: 1.98542ms message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:19:16Z" - latency: 1.88749ms message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:18:16Z" - latency: 2.350917ms message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:17:16Z" - latency: 2.054017ms message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:16:16Z" - latency: 2.389348ms message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:15:16Z" - latency: 2.17721ms message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:14:16Z" - latency: 2.461812ms message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:13:16Z" - latency: 2.248159ms message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:12:16Z" - latency: 2.488691ms message: 'network-check-target-ip-10-0-137-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:11:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:38:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-199-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-199.ec2.internal uid: 4952478e-9274-454c-ba18-190a2d4e0453 resourceVersion: "71007" uid: d5c3e8ed-2b75-49f1-9de7-01c428776feb spec: sourcePod: network-check-source-7d88cb55d8-5x9s7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T13:44:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 848.635µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:20:16Z" - latency: 1.831579ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T14:20:16Z" - latency: 1.258169ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:19:16Z" - latency: 1.995493ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T14:19:16Z" - latency: 862.621µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:18:16Z" - latency: 1.932317ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T14:18:16Z" - latency: 888.871µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:17:16Z" - latency: 1.805107ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T14:17:16Z" - latency: 1.075131ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:16:16Z" - latency: 1.811378ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T14:16:16Z" kind: List metadata: resourceVersion: ""